Skip to main content
Glama
vish288

mcp-argocd

by vish288
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Argocd Get Applicationset

argocd_get_applicationset
Read-onlyIdempotent

Retrieve one Argo CD ApplicationSet to inspect its generators, sync strategy, and generated application statuses.

Instructions

Get one ApplicationSet: generators, strategy, and the status of the apps it generates.

Input Schema

NameRequiredDescriptionDefault
fullNoReturn the raw API payload instead of the slim one
nameYesApplicationSet name
appset_namespaceNoApplicationSet namespace
include_templateNoInclude the full spec.template
include_applicationsNoInclude generated app statuses

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.6/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 useful content context by naming the returned fields, but says nothing about the effect of the full/include_template/include_applications flags or namespace defaulting.

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 well-formed sentence that front-loads the action and resource and packs the return contents without waste.

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 no output schema, the description partially compensates by summarizing the returned shape (generators, strategy, generated-app statuses), and annotations cover safety. It is adequate for a read-only getter, though it does not explain how the include flags alter the response.

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 five parameters, so the schema fully documents name, namespace, full, include_template, and include_applications. The description adds no syntax or defaulting detail beyond that, making the baseline 3 appropriate.

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 one ApplicationSet') and enumerates what is returned (generators, strategy, generated-app status), which distinguishes it from the list and generate siblings. It does not explicitly name an alternative tool, so it stops short of a 5.

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

Usage Guidelines3/5

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

'Get one' implies single-resource retrieval as opposed to argocd_list_applicationsets, but there is no explicit when-to-use/when-not guidance and no pointer to a sibling such as argocd_generate_applicationset. Usage is inferable but not stated.

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