Loading ToolBench
MCP server for Devtron — manage apps, pipelines, and deployments via Claude
The server defines 11 tools with reasonable coverage for Devtron CI/CD operations. Tool naming follows verb_noun conventions consistently (list_*, get_*, trigger_*, check_*), making intent clear. All tools have descriptions (7 - 180 chars), exceeding the 10-char minimum. Input schemas are present and properly typed for all tools. However, several gaps limit the score: (1) Parameter descriptions are sparse or missing for some tools, e.g., devtron_trigger_ci_build's 'ciMaterials' array lacks detail on expected object structure; (2) No output schemas are documented, LLMs cannot predict what fields to expect, breaking downstream tool chaining; (3) Error handling is absent from the visible code, no guidance on retries, recovery, or actionable error messages; (4) Most tools lack dependency hints (e.g., 'Use devtron_list_apps first to find an app ID'); (5) No pagination guidance for list tools, despite the likelihood of large result sets. The tools are straightforward and well-named, but the lack of output schemas and sparse parameter details prevent a higher score.
Check the current deployment status of a Devtron application in a specific environment. Returns running pod counts, pre/post stage statuses, the deployed image tag, and when the last deployment occurred. Poll this tool after triggering a deployment to confirm it completed successfully.
Retrieve details for a specific Devtron application by its numeric app ID.
Retrieve detailed information about a specific Kubernetes cluster by its ID.
Get the current deployment status for a Devtron application in a specific environment. Returns pod counts, pipeline stage statuses, image tag, and last deploy time.
Retrieve the deployment (release) history for a Devtron application in a given environment. Useful for auditing past deployments and identifying the images that were shipped.
No output schemas documented. LLMs cannot predict return structure, breaking tool chaining and forcing extra discovery calls. Pattern requires 'Document the output schema' so agents plan downstream calls.
Parameter 'ciMaterials' in devtron_trigger_ci_build lacks actionable description. The description states 'Optional array of git material override objects. Each item may contain { id, gitMaterialId, type, value }' but does not specify which fields are required, allowed values for 'type', or example structure. LLM will guess.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 56 | 2026-07-28+ | v2 |
| 2026-03-09 | D | 50 | - | v1 |
List all applications registered in Devtron. Optionally filter by team ID to scope results to a specific team.
List all CI (Continuous Integration) pipelines associated with a Devtron application. Returns pipeline IDs, names, and current status useful for selecting a pipeline to trigger.
List all Kubernetes clusters registered in Devtron. Returns cluster IDs, names, API server URLs, and whether each cluster is active.
List all deployment environments configured for a Devtron application. Returns environment names, namespaces, and associated cluster information.
Trigger a CI build run for a Devtron application. Provide the CI pipeline ID and optional git material overrides (branch or commit hash). If no ciMaterials are supplied, the pipeline uses its default branch configuration.
Trigger a CD (Continuous Deployment) deployment in Devtron. You need the app ID, the CD pipeline ID for the target environment, and the CI artifact ID (container image) to deploy. Use devtron_get_release_history or devtron_get_deployment_status to find artifact IDs.
No error handling guidance in visible code. Tools provide no actionable error messages (e.g., 'User not found. Try search_users() with a partial name.'). LLMs cannot determine whether to retry, ask the user, or abort.
List tools (devtron_list_apps, devtron_list_environments, devtron_list_ci_pipelines, devtron_list_clusters) lack pagination parameters (limit, offset/page, cursor) and no description mentions result limits. Without pagination, large result sets will blow the context window.
No dependency hints or multi-step guidance. For example, devtron_trigger_deployment requires ciArtifactId but does not hint 'Use devtron_get_release_history() first to find available artifact IDs.' LLMs must infer the workflow, wasting reasoning cycles.
WRITE operations (devtron_trigger_ci_build, devtron_trigger_deployment) lack confirmation/dry-run pattern. These are irreversible CI/CD actions that could trigger builds or deployments. Agents should have a chance to preview before committing.
Parameter type annotations missing or incomplete. E.g., devtron_trigger_ci_build accepts 'appId' and 'ciPipelineId' as numbers, but no description specifies the valid range or how to obtain them. LLMs may pass invalid IDs, causing silent failures.