Skip to main content
Glama

Confirm service retirement

confirm_service_retirement
Destructive

Confirm a prepared retirement and DELETE the managed service and its data (step two of ankra services delete). The digest must be the one prepare_service_retirement returned: a plan that changed since, or that expired, is refused. This cannot be undone. Follow it with get_service_retirement until it settles. Requires applications.deploy and stacks.delete.

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": {
      "instance_id": "<instance_id>",
      "retirement_id": "<retirement_id>",
      "digest": "<digest>"
    },
    "name": "confirm_service_retirement"
  }
}

Input Schema

NameRequiredDescriptionDefault
digestYesThe retirement's digest from prepare_service_retirement.
instance_idYesService instance id (UUID).
retirement_idYesRetirement id (UUID) from prepare_service_retirement.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations' destructiveHint=true, the description adds material context: the action is irreversible ('This cannot be undone'), it deletes the service plus its data, it fails if the plan drifted or expired, and it requires applications.deploy and stacks.delete permissions. That is exactly the behavioral disclosure needed for a destructive mutation.

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?

Four short sentences, front-loaded with the destructive action, then constraints, then the follow-up, then permissions. No filler and nothing important buried.

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

Completeness5/5

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

For a three-parameter destructive tool with no output schema, the description covers the lifecycle position, the irreversibility, the failure mode, the post-call verification step, and the required scopes — everything an agent needs before invoking it.

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 goes further by stating the digest must be the one returned by prepare_service_retirement and that a stale or expired plan is rejected — semantics the schema fields alone do not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Confirm a prepared retirement and DELETE the managed service and its data') and places it in the two-step flow of `ankra services delete`, which separates it cleanly from prepare_service_retirement and get_service_retirement.

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

Usage Guidelines5/5

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

Explicitly names the prerequisite (digest returned by prepare_service_retirement), the follow-up call (get_service_retirement until it settles), and the refusal condition (plan changed or expired). An agent knows exactly when this tool is applicable and what must precede and follow it.

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.