Skip to main content
Glama

Resolve a name or retired identifier

resolve_name
Read-onlyIdempotent

Turn a display name, an identifier or a retired identifier into the current identifier (for example export_pressure becomes export_earnings_shock). If nothing matches it says so and returns the closest three candidates.

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

Input Schema

NameRequiredDescriptionDefault
nameYesDisplay name, identifier or retired identifier. Not empty.

Output Schema

NameRequiredDescriptionDefault
idNo
urlNo
nameNo
noteNo
foundYes
layerNo
matchNo
queryYes
scopeNoScope of the registry: what the entries are and are not.
versionYes
candidatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: on a miss it reports the failure and returns the three nearest candidates, which tells the agent how to recover. It does not address ambiguity (multiple matches), case sensitivity, or whether resolution is exact or fuzzy, leaving some gaps.

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?

Two sentences, front-loaded with the core transformation and followed by the failure path. No filler, no restatement of the title, and the parenthetical example earns its place by making the rename pattern concrete.

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?

With an output schema present and full annotation coverage, the description needn't explain return values, and it correctly focuses on the fallback path. What remains unstated is how ties or multiple candidate matches are handled, which matters for a resolver that can return three candidates.

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% with a single documented parameter ('Display name, identifier or retired identifier. Not empty.'), so the schema already carries the semantics. The description restates the accepted input kinds and supplies one example pair, adding only marginal value beyond the structured field.

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 transformation (display name / identifier / retired identifier → current identifier) with a concrete mapping example, which is clearly distinct from siblings like search or fetch that return lists or content rather than resolving identity. An agent can predict the output shape from the first sentence alone.

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?

Usage is implied by the input contract: call it when you hold a name or retired id and need the live id. However, no alternative is named and no exclusion is stated (e.g. 'do not use this to look up by topic — use search instead'), so the agent must infer routing from sibling names alone.

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.