AgentStamp

get_agent

Retrieve a complete agent profile using its ID to access endorsements and a reputation score. Ideal for verifying agent trustworthiness.

Instructions

Get full agent profile by ID, including endorsements and reputation score.

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_id": "<agent_id>"
    },
    "name": "get_agent"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes	The agent ID (e.g., agt_E-PFtTAIQlfVleNm)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Mar 22, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the burden of disclosing behavior. It indicates a read operation and lists returned content (endorsements, reputation score), but does not mention potential errors, authentication requirements, or response format. This is adequate but not rich.

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?

The description is a single sentence that is direct and front-loaded. Every word contributes to explaining the tool's purpose and key outputs.

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?

For a simple get-by-ID tool with one well-documented parameter and no output schema, the description sufficiently explains what the tool does and what it returns. No additional context is necessary.

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% for the single parameter, so the schema already documents agent_id well. The description only says 'by ID', adding no extra semantic detail beyond what the schema provides.

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?

The description clearly states the verb 'Get' and the resource 'full agent profile by ID', and specifies that it includes endorsements and reputation score. This distinguishes it from siblings like get_agent_reputation and browse_agents.

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?

The phrase 'by ID' implies this is appropriate when the agent ID is known and a full profile is desired. However, it does not explicitly mention when to prefer this over alternatives like get_agent_reputation or search_agents.

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