Skip to main content
Glama
Sign In

Opsphere — DevOps & SRE Intelligence

by io.opsphere.mcp-cursor
OverviewDiscussionsAdmin

ArgoCD: Get Application detail

argocd_get_app
Read-only

Returns the full ArgoCD Application CRD for a specific app. Includes spec (source, destination, syncPolicy) and status (sync, health, resources, conditions, operationState).

Input Schema

NameRequiredDescriptionDefault
nameYesApplication name (from argocd_list_apps or tenant catalog)
profileNoOptional AWS profile override for management-cluster kubectl authentication. OMIT to preserve the installation management identity (recommended). Do not substitute the destination account/environment profile. Explicit overrides are checked against configured valid_profiles. SSO requirements and Kubernetes permissions remain enforced.
instanceNoArgoCD installation in the active workspace. Read opsphere://argocd/installations for mode and identifiers. In active mode, use an installation slug; an exact environment association or unique migrated alias is also accepted. Omit only when there is one installation. Legacy/shadow modes retain existing catalog aliases and defaults.
context_idNoOptional explicit Connection Hub work context (ctx_*). Omit to use the conversation's active workspace; global Hub tools ignore it.

Output Schema

NameRequiredDescriptionDefault
okYes
dataYes
contractVersionYes
dataSchemaVersionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changed
    • changedOutput schema / properties / data / additionalProperties
      Previous value: -trueNew value: +false
    • removedOutput schema / properties / data / properties / app / $ref
      Removed value: -"#/properties/data/properties/items/items"
    • addedOutput schema / properties / data / properties / app / additionalProperties
      Added value: +false
    • addedOutput schema / properties / data / properties / app / properties
      Added value: +{
+  "cluster": {
+    "type": "string"
+  },
+  "healthStatus": {
+    "enum": [
+      "Healthy",
+      "Progressing",
+      "Degraded",
+      "Suspended",
+      "Missing",
+      "Unknown"
+    ],
+    "type": "string"
+  },
+  "name": {
+    "type": "string"
+  },
+  "namespace": {
+    "type": "string"
+  },
+  "project": {
+    "type": "string"
+  },
+  "revision": {
+    "type": "string"
+  },
+  "syncStatus": {
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / data / properties / app / required
      Added value: +[
+  "name"
+]
    • addedOutput schema / properties / data / properties / app / type
      Added value: +"object"
    • removedOutput schema / properties / data / properties / applications
      Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}
    • removedOutput schema / properties / data / properties / clusters
      Removed value: -{
-  "$ref": "#/properties/data/properties/items"
-}
    • addedOutput schema / properties / data / properties / conditions
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "message": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "message"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / data / properties / count
      Removed value: -{
-  "type": "number"
-}
    • addedOutput schema / properties / data / properties / gaps
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / data / properties / items
      Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / data / properties / lastSyncedAt
      Added value: +{
+  "format": "date-time",
+  "type": "string"
+}
    • addedOutput schema / properties / data / properties / partial
      Added value: +{
+  "type": "boolean"
+}
    • removedOutput schema / properties / data / properties / resources / $ref
      Removed value: -"#/properties/data/properties/items"
    • addedOutput schema / properties / data / properties / resources / items
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "health": {
+      "$ref": "#/properties/data/properties/app/properties/healthStatus"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "namespace": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "name"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / data / properties / resources / type
      Added value: +"array"
    • addedOutput schema / properties / data / properties / truncated
      Added value: +{
+  "type": "boolean"
+}
    • addedOutput schema / properties / data / properties / warnings
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / data / required
      Added value: +[
+  "app",
+  "partial",
+  "truncated",
+  "warnings",
+  "gaps"
+]
    • addedOutput schema / properties / dataSchemaVersion
      Added value: +{
+  "const": 2,
+  "type": "number"
+}
    • changedOutput schema / required
      Previous value: -[
-  "contractVersion",
-  "ok",
-  "data"
-]New value: +[
+  "contractVersion",
+  "dataSchemaVersion",
+  "ok",
+  "data"
+]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-destructive, non-open-world operation. The description adds useful scope by listing the spec and status content returned, but it does not disclose any additional behavioral context such as authentication requirements or limitations beyond what the schema and annotations provide.

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?

The description is two tightly written sentences with the core purpose front-loaded. Every sentence contributes useful information, and there is no filler.

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?

Given the read-only annotations, complete parameter descriptions, and the existence of an output schema, the description is largely complete for invocation. Its main missing piece is sibling differentiation, which would help an agent choose this tool over other ArgoCD detail 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 four parameters are already well documented in the input schema. The description only implies that a specific application name is required and adds no extra semantics beyond the schema, which matches the baseline for fully documented parameters.

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?

The description uses a specific verb and resource: it returns the full ArgoCD Application CRD for a named app. It also names the main contents (spec and status fields), making the tool's purpose clear. However, it does not distinguish this tool from sibling ArgoCD tools such as argocd_app_resources or argocd_app_unhealthy.

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 implies usage by saying it returns a specific app's full CRD, but it gives no explicit guidance on when to use this tool versus alternatives. With several ArgoCD siblings available, the absence of routing guidance is a clear gap.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Opsphere — DevOps & SRE Intelligence toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources