Skip to main content
Glama
vish288

mcp-argocd

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Argocd Get Managed Resources

argocd_get_managed_resources
Read-onlyIdempotent

Retrieve managed resources for an Argo CD application with live-vs-desired diffs, filter by kind/namespace/group, and optionally include parsed target/live/predicted states.

Instructions

Get managed resources with their live-vs-desired diffs (truncated by default).

include_states adds the parsed target, normalized-live, and predicted-live manifests with managedFields stripped.

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by kind
nameYesApplication name; accepts namespace/name for apps-in-any-namespace
groupNoFilter by API group
projectNoProject; with it a missing app is 404 and a wrong-project app is 403
versionNoFilter by API version
namespaceNoFilter by namespace
app_namespaceNoOverride appNamespace; defaults to ARGOCD_APP_NAMESPACE
modified_onlyNoOnly resources with a live-vs-desired diff
resource_nameNoFilter by resource name
include_statesNoInclude parsed target/live/predicted states
max_diff_charsNoTruncate each diff to this many chars

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

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description still adds real behavioral value: default truncation of diffs and the side effect that include_states injects parsed target/normalized-live/predicted-live manifests with managedFields stripped, which is not in the annotations.

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

Conciseness4/5

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

Two tight sentences with no filler; the core behavior (diff retrieval, truncated by default) is front-loaded before the include_states elaboration. Slightly dense/technical but every clause earns its place.

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 11 parameters, no output schema, and only 1 required parameter, the description covers the key output-shaping flags but says nothing about the overall return structure, the effect of the sibling filter parameters, or how results are paged/limited. Adequate given the 100% schema coverage and read-only annotations, but not complete.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description meaningfully elaborates on include_states beyond the schema's terse 'Include parsed target/live/predicted states' by explaining the manifests added and that managedFields are stripped, and confirms the diff-truncation semantics behind max_diff_chars.

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 and resource ('Get managed resources') plus the salient output characteristic (live-vs-desired diffs, truncated by default). It is clear what the tool returns, though it never names or contrasts with overlapping siblings such as argocd_get_resource_tree, argocd_get_resource, or argocd_get_manifests.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternative tools for inspecting application resources. The only implicit context is that diffs are truncated by default and include_states expands output, which hints at usage but does not guide tool selection.

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