Skip to main content
Glama
vish288

mcp-argocd

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Argocd Get Revision Metadata

argocd_get_revision_metadata
Read-onlyIdempotent

Get commit metadata for an Argo CD app revision: author, date, message, tags, and signature info. Use it to inspect Git history details for a specific revision.

Instructions

Get commit metadata for a revision: author, date, message, tags, signature info.

Input Schema

NameRequiredDescriptionDefault
nameYesApplication name; accepts namespace/name for apps-in-any-namespace
projectNoProject; with it a missing app is 404 and a wrong-project app is 403
revisionYesGit revision or chart version
version_idNoHistory version id
source_indexNoSource index for multi-source apps
app_namespaceNoOverride appNamespace; defaults to ARGOCD_APP_NAMESPACE

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.2/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 safety/idempotency are covered by structured data. The description adds the set of returned fields, which is genuinely useful given no output schema exists, but says nothing about failure modes (e.g., invalid revision) or the effect of project/version_id on lookup.

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?

A single front-loaded sentence with no filler; the most important information (what is fetched) leads. Slightly terse — it allocates no space to usage or behavioral context.

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

Completeness4/5

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

For a read-only lookup with full schema coverage and annotations, the remaining need is knowing what comes back — and the description enumerates the returned fields, compensating for the absent output schema. Error behavior and revision-format expectations are the only notable gaps.

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%, with each of the six parameters already documented (including the 404/403 semantics of project). The description adds no parameter-level meaning beyond the schema, 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 resource ('commit metadata for a revision') and enumerates the returned fields (author, date, message, tags, signature info). No sibling tool covers revision/commit metadata, so the boundary is implicitly clear, though it never names an alternative.

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 offers no when-to-use guidance, prerequisites, or alternatives — it only describes the payload. An agent gets no signal about when this is preferable to, say, argocd_get_application_history or argocd_get_manifests.

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