Skip to main content
Glama
vish288

mcp-argocd

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Argocd Patch Application

argocd_patch_application
Idempotent

Patch Argo CD applications by applying JSON merge or RFC 6902 patches to update specs, change target revisions, or disable auto-sync.

Instructions

Patch an application — the one tool for every update.

Examples: change targetRevision with patch='{"spec":{"source":{"targetRevision":"v2"}}}'; disable auto-sync with patch='{"spec":{"syncPolicy":{"automated":null}}}'.

Input Schema

NameRequiredDescriptionDefault
nameYesApplication name; accepts namespace/name for apps-in-any-namespace
patchYesJSON patch body
projectNoProject; with it a missing app is 404 and a wrong-project app is 403
patch_typeNomerge (RFC 7386) or json (RFC 6902)merge
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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds no behavioral context beyond that — no mention of permissions, partial-failure semantics, or what a failed patch returns. Adequate but not additive.

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?

Two sentences, zero waste, front-loaded with the purpose before the payload examples. Every clause earns its place.

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?

With full schema coverage, annotations covering the safety profile, and no output schema to explain, the description supplies the missing payload guidance. It could go further on merge-vs-json patch implications, but nothing essential for calling the tool is absent.

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 earns extra credit by supplying concrete patch payload examples for the required 'patch' string parameter — exactly the kind of syntax the schema's 'JSON patch body' line does not convey. This is genuine value beyond the structured fields.

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+resource ('Patch an application') and adds the routing phrase 'the one tool for every update', which distinguishes it from create/delete/sync/rollback siblings. It stops short of naming a specific sibling, but the scope claim is clear.

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

Usage Guidelines4/5

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

The phrase 'the one tool for every update' plus two concrete examples (change targetRevision, disable auto-sync) give a clear sense of when to reach for this tool. No explicit when-not or negative routing is provided, so it isn't a full 5.

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