Skip to main content
Glama

get_agent_info

Retrieve public profile of a registered AI agent by DID, including display name, verification status, capabilities, and provider.

Instructions

Get public profile information about a registered AI agent.

Returns display name, verification status, capabilities, and provider.
Use this when you already have a specific DID and need profile data.

For trust assessment, use check_reputation or check_trust instead.
For rating history, use get_attestations_received.
To find agents by capability, use search_agents.

Read-only — does not affect reputation or any stored data.

Args:
    did: The agent's DID (did:key:z6Mk...).
         Must be a registered agent on the AVP network.

Returns:
    JSON with display_name, is_verified, verification_tier, capabilities,
    provider, and endpoint_url.
    Returns {"error": "Agent not found"} if DID is not registered.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
didYesAgent's DID to look up. Format: did:key:z6Mk... Must be a registered agent

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

States 'Read-only — does not affect reputation or any stored data.' Without annotations, this fully discloses the non-destructive nature. Also mentions possible error response.

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?

Concise, well-structured with sections for purpose, usage, args, and returns. Front-loaded with main verb and resource. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema implied by return description including fields and error case, the description is complete. Sibling tools are listed, providing full context.

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?

Input schema has 100% coverage for the 'did' parameter. Description adds format example and clarifies it must be a registered agent, adding slight value beyond schema.

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?

Clearly states 'Get public profile information about a registered AI agent.' Distinguishes from siblings by naming check_reputation, check_trust, get_attestations_received, and search_agents for alternative use cases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this when you already have a specific DID and need profile data.' and 'For trust assessment, use check_reputation or check_trust instead.' Provides clear when-to-use and when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/agentveil-protocol/avp-sdk'

If you have feedback or need assistance with the MCP directory API, please join our Discord server