Skip to main content
Glama

Get service retirement

get_service_retirement
Read-only

Read one retirement of a managed service (the twin of ankra services retirements get): its reviewed plan, state and phase, its outcome once settled, and what became of each reviewed volume once the namespace was gone. A retirement whose outcome is retired released the name; its data_disposal says whether the service's data may remain (data_kept, unconfirmed) and kept_data names the volumes, the cluster, when Ankra last looked and the Ankra CLI commands to inspect or erase them. Never report such a service as plainly deleted, and say kept_data is what Ankra saw then, not now. Use it to follow confirm_service_retirement until it settles. Read-only.

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>"
    },
    "name": "get_service_retirement"
  }
}

Input Schema

NameRequiredDescriptionDefault
instance_idYesService instance id (UUID).
retirement_idYesRetirement id (UUID) from prepare_service_retirement or get_service_instance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true; the description goes far beyond by explaining outcome semantics ('retired' released the name), the meaning of data_disposal values (data_kept, unconfirmed), what kept_data contains (volumes, cluster, last-look timestamp, CLI commands), and a critical caveat that kept_data is a point-in-time observation rather than current truth.

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?

Front-loads the core purpose before the detail, and nearly every clause carries operational meaning. However it is a single dense paragraph with run-on clauses ('Never report such a service as plainly deleted, and say kept_data is what Ankra saw then, not now') that would scan better as structured statements.

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?

There is no output schema, so the description must carry the return-value burden, and it does: it describes the plan, state/phase, settled outcome, per-volume dispositions, and the kept_data structure. An agent has enough to interpret the response and report it accurately.

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 coverage is 100% and both required parameters are already documented in the schema, including where retirement_id comes from. The description adds no additional meaning about instance_id or retirement_id, so the baseline 3 applies.

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?

Opens with a specific verb+resource and explicit scope: 'Read one retirement of a managed service', then enumerates what is returned (reviewed plan, state and phase, outcome, per-volume fate). It names its CLI twin and is clearly distinguishable from prepare_service_retirement, confirm_service_retirement, and get_service_instance.

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?

Gives explicit usage context: 'Use it to follow confirm_service_retirement until it settles', which ties it to a specific workflow step and implies repeated polling until a terminal state. It does not explicitly state when not to use it (e.g. to list retirements, or to prepare/confirm one), so it falls short of the full when/when-not/alternatives bar.

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.