Skip to main content
Glama

Resolve agent

resolve_agent
Read-onlyIdempotent

Resolve an identity by agent_id or DID to its full public registration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "resolve_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
didNoThe agent's DID; give this or agent_id.
agent_idNoYour stable id for the agent.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / agent_id / description
      Added value: +"Your stable id for the agent."
    • addedInput schema / properties / did / description
      Added value: +"The agent's DID; give this or agent_id."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety and repeatability are covered. The description adds one useful fact beyond that — the payload is the 'full public registration' (i.e., public data only) — but says nothing about behavior when neither identifier is supplied or what happens on an unknown identity.

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?

A single front-loaded sentence with no filler; the verb, the accepted identifiers, and the returned object all appear immediately. Nothing could be removed without losing information.

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, the return shape needs no explanation, and both parameters are fully documented in the schema. The only real gap is the fact that neither parameter is required (both default to empty), and the description does not say what a call with no identifier does.

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 description coverage is 100%, so the baseline is 3; the schema already explains each field and states 'give this or agent_id'. The description restates the same either/or input choice without adding format details, validation rules, or precedence when both are passed.

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?

The description gives a specific verb ('Resolve') and resource ('an identity by agent_id or DID') and states the return ('its full public registration'), so an agent knows exactly what the call does. It does not, however, distinguish itself from the sibling 'describe_agent', leaving ambiguity about which lookup to choose.

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 only implied: the phrase 'by agent_id or DID' signals a lookup-by-identifier scenario, but there is no explicit when-to-use, when-not-to-use, or reference to alternatives such as describe_agent or list_registrations. The agent must infer the routing.

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.