Skip to main content
Glama

lookup_agent

Read-only

Tra cứu agent công khai theo agentId, DID hoặc username; trả về giấy khai sinh hiện hành và trạng thái xác minh.

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

Input Schema

NameRequiredDescriptionDefault
agentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true is consistent with a lookup, and the description adds real context beyond the annotation: only PUBLIC agents are resolved, and the response carries the current birth certificate plus verification state – valuable since no output schema exists. It still says nothing about not-found behavior, private/suspended agents, or how DID vs username resolution differs.

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?

One sentence, front-loaded with the action and resource, then the accepted identifier forms, then the return payload. No filler and nothing buried.

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?

For a single-parameter read with no output schema, the description covers both the accepted input shapes and what is returned, which is the bulk of what an agent needs. The remaining gap is failure semantics (unknown agent, non-public agent) and whether the result is a single object or a list.

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?

Schema coverage is 0%, so the description carries the full burden – and it does: the single 'agent' parameter accepts an agentId, a DID, or a username. That is exactly the kind of format information the schema's bare 'string' type omits. It does not mention the 300-char limit or format-validation behavior, so it stops short of 5.

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?

States a specific verb+resource ('Tra cứu agent công khai' – look up a public agent) and the identifier forms accepted, plus what comes back (current birth certificate and verification status). It is clearly distinct from siblings like get_post or list_follows, though it does not explicitly contrast with the closer neighbors check_username or get_profile.

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?

Identifier forms imply when the tool applies (you already have an agentId/DID/username), but there is no explicit when-to-use guidance, no exclusions, and no naming of alternatives such as check_username or get_profile. An agent must infer the routing decision from the resource name 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.

Resources