Skip to main content
Glama

retire_key

Stop returning a key's values with a permanent retirement. Supersede every active record with a reason so recall no longer returns it while history preserves its full record and retired policy.

Instructions

END a key with NO replacement. Every active value for key becomes superseded with reason on the record and in the receipt chain; nothing new is written, so recall stops returning it and history(key) still shows every value it held with policy "retired" and the reason. Use it when a key no longer applies (moved, renamed, withdrawn). A remember with a placeholder value would do the opposite: it leaves a new ACTIVE value standing. Returns {key, retired, ids, reason, status, policy}: the records read status: "superseded" with meta.superseded_by_policy: "retired"; there is no retired status to filter on.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
reasonYes
sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.1.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations are present, so this description bears the full disclosure burden. It explains there are no new writes, that `recall` stops returning the key, that `history(key)` retains values with policy 'retired', and the exact status/metadata returned. It even warns there is no `retired` status to filter on, preventing a likely misconception.

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 long but dense and front-loaded; the first clause states the operation and core constraint before any detail. Each subsequent clause adds actionable semantics (effects on recall/history, usage trigger, return shape) rather than padding.

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 tool with no annotations and no output schema, the description covers the essential context: when to use, what changes, what doesn't change, what the response contains, and a common gotcha about status filtering. The only minor gap is the `source` parameter, which is optional and does not undermine completeness for calling the tool correctly.

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?

The input schema has 0% description coverage (only titles 'Key', 'Reason', 'Source'), so the description must compensate. It clarifies what `key` and `reason` do semantically: superseding active values and stamping the reason into the record and receipt chain. `source` remains completely undocumented, which prevents a perfect score.

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?

The description uses a concrete verb and resource ('END a key') and immediately limits scope ('with NO replacement'). It names the opposite operation (`remember` with placeholder) so an agent can distinguish it from that sibling. The effect on `recall`/`history` further clarifies what it is for.

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?

Explicit trigger enumerated: 'Use it when a key no longer applies (moved, renamed, withdrawn).' It also gives an explicit alternative and contrasting behavior: `remember` with placeholder would leave a new ACTIVE value, so an agent knows not to choose that for retirement.

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