Skip to main content
Glama

Reconcile application

reconcile_application
Destructive

Reconcile an Application: re-run the platform's convergence for its resources and pipeline wiring. Safe, idempotent.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application_id": "<application_id>"
    },
    "name": "reconcile_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior1/5

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

The description asserts 'Safe, idempotent,' while the annotations declare readOnlyHint=false, idempotentHint=false, and destructiveHint=true. This is a direct contradiction of the structured safety profile, and no accurate behavioral context (what may be torn down, downtime risk, permissions) is provided.

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?

Two short sentences with the operation front-loaded and no filler. The trailing 'Safe, idempotent' clause is compact but misleading rather than useful, which costs it a point.

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

Completeness2/5

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

For a destructive, non-idempotent mutation with no output schema, the description should explain impact, reversibility, and any prerequisites. Instead it supplies a false safety claim, leaving an agent without the information needed to invoke it responsibly.

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?

There is a single required parameter with 100% schema description coverage, so the schema already carries its meaning. The description adds nothing about application_id (format, where to obtain it, or what happens if it is unknown), so 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+resource ('Reconcile an Application') and explains the operation concretely as re-running the platform's convergence for resources and pipeline wiring, which an agent can distinguish from sibling read/create/delete tools by resource and action. It stops short of explicitly contrasting with reconcile_cluster.

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?

The phrase 're-run the platform's convergence' implies the use case (recovering drifted or failed state), but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g., deploy_application, retry_application, reconcile_cluster).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.