resolve_agent
Resolve an identity by agent_id or DID to its full public registration.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| did | No | ||
| agent_id | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Resolve an identity by agent_id or DID to its full public registration.
| Name | Required | Description | Default |
|---|---|---|---|
| did | No | ||
| agent_id | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. Description implies a read-only lookup but does not confirm idempotency, side effects, or rate limits. Lacks detail on behavior beyond the basic operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no extra words. Adequate but not structured to highlight key information like parameter choices or output context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite having an output schema (not shown), the description does not mention what the output contains. Parameter documentation is absent. The tool is simple but still incomplete for an AI agent to use confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema has 0% description coverage. The description only mentions parameters by name ('agent_id or DID') but does not explain their semantics, constraints, or when each should be used. Adds almost no value over the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states it resolves an identity to its full public registration via agent_id or DID. The verb 'resolve' and resource 'identity registration' are specific, but does not distinguish from sibling 'describe_agent' which may provide similar details.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus siblings like describe_agent or discover_agents. No mention of prerequisites, alternatives, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.