Skip to main content
Glama
vish288

mcp-argocd

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Argocd Get Manifests

argocd_get_manifests
Read-onlyIdempotent

Retrieve rendered desired manifests for an Argo CD application revision, parsed into objects with paging and filtering.

Instructions

Get the rendered desired manifests for a revision, parsed into objects and paged.

Input Schema

NameRequiredDescriptionDefault
kindNoClient-side kind filter
nameYesApplication name; accepts namespace/name for apps-in-any-namespace
limitNoMax results to return (1-200)
offsetNoResult offset for paging
projectNoProject; with it a missing app is 404 and a wrong-project app is 403
revisionNoRevision to render
app_namespaceNoOverride appNamespace; defaults to ARGOCD_APP_NAMESPACE
resource_nameNoClient-side name filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: results are parsed into discrete objects and are paged. It stops short of describing error behavior, though the schema's 'project' field hints at 404/403 semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; every clause ('rendered desired', 'for a revision', 'parsed into objects', 'paged') carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should carry more of the return-shape burden; 'parsed into objects' is helpful but the object structure and paging envelope remain unspecified. For an 8-parameter read tool this is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% across all 8 parameters, including non-obvious semantics for name (namespace/name form), project (404 vs 403), and app_namespace (ARGOCD_APP_NAMESPACE default). The description adds nothing parameter-level, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Get') and a precisely scoped resource ('rendered desired manifests for a revision'), plus the output shape ('parsed into objects and paged'). This implicitly distinguishes it from live-state siblings like argocd_get_managed_resources or argocd_get_resource, though no sibling is named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no when-to-use guidance, no exclusions, and never names an alternative (e.g. argocd_get_managed_resources for live objects, argocd_get_application for app metadata). An agent must infer the selection criteria from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools