Retrieve a full profile for a specific agent or endpoint by its numeric ID or identifier URI. Returns protocol detection, liveness history, on-chain payment evidence, MCP tools list, and A2A skills.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric ID (e.g. 42) or full identifier URI (e.g. urn:air:huggingface.co:skill:abc) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Mentions specific return content (protocol detection, liveness history, etc.), implying read-only behavior. No contradictions.
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?
Two concise sentences: first states purpose, second lists return contents. No unnecessary words, highly scannable.
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?
Single-parameter tool with no output schema; description adequately lists return categories. No missing context for selection and invocation.
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?
Single parameter 'id' with schema coverage 100%. Description redundantly mentions ID type but adds no new semantics beyond schema's detailed example.
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 explicitly states the verb 'retrieve' and resource 'full profile', with specific identifiers (numeric ID or identifier URI). Clearly distinguishes from sibling tool 'search_agents' by focusing on individual profile retrieval.
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?
Indicates usage via numeric ID or URI, providing clear context. Lacks explicit when-not or alternatives, but the sibling name 'search_agents' implies when to use this instead.
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.
Each tool has a clearly distinct purpose: bulk export, individual profile retrieval, demand preview vs. full report, endpoint change alerts, liveness history, trust score, and search. No overlapping functionality.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (get_*, bulk_export, search_agents). No mixed conventions or irregular naming.
8 tools is well-scoped for an agent index service, covering search, retrieval, export, and monitoring without excess or redundancy.
The tool set covers the full lifecycle of interacting with an agent index: search, retrieve profiles, bulk export, monitor changes, and assess liveness/trust/demand. No obvious gaps in functionality.