Skip to main content
Glama
vish288

mcp-argocd

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Argocd Get Application History

argocd_get_application_history
Read-onlyIdempotent

Retrieve an Argo CD application's deployment history, newest first, including revision, who deployed it, and source, to audit changes or investigate rollbacks.

Instructions

Get deployment history (newest first) with revision, who deployed it, and the source.

Input Schema

NameRequiredDescriptionDefault
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
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 this as a safe, idempotent, read-only operation, so the safety profile is covered. The description usefully adds result ordering (newest first) and the returned fact set, but says nothing about paging behavior or volume despite limit/offset parameters.

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 tight sentence that front-loads the operation and then lists the returned fields and ordering. Nothing is redundant, though it is arguably terse enough to leave gaps.

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 paged history lookup with a fully documented schema and no output schema, the description covers what the tool returns and its ordering. The main omissions are guidance on paging and on choosing this over adjacent history/event tools.

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%, so all five parameters (name, limit, offset, project, app_namespace) are already documented in the schema, including the 404/403 semantics for project. The description adds no parameter-level detail, 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 and resource (get deployment history for an application) and even summarizes the payload: revision, who deployed, and the source, ordered newest first. It is clearly separable from siblings like argocd_get_application_events or argocd_get_revision_metadata, though it never explicitly names those alternatives.

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 guidance and no mention of alternatives. An agent must infer that this is for historical deployment inspection rather than current state, and nothing tells it whether to prefer this over argocd_get_application_events or argocd_get_operation.

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