AgentStamp

get_agent_reputation

Retrieve a comprehensive reputation score (0-100) for any AI agent, with detailed breakdown by tier, endorsements, uptime, age, and wishes granted.

Instructions

Get an agent's reputation score (0-100) with full breakdown by tier, endorsements, uptime, age, and wishes granted.

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_reputation"
  }
}

Input Schema

Name	Required	Description	Default
`agent_id`	Yes	The agent ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Mar 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses the score range and the breakdown dimensions of the return value, but it omits error behavior, data freshness, permissions, or what happens for unknown agents. This is a useful but limited behavioral disclosure.

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, well-structured sentence. It front-loads the action and resource ('Get an agent's reputation score') and then appends the detail about the score range and breakdown. No unnecessary words or restatements.

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 simple one-parameter read-only tool, the description adequately covers the main purpose and return content. It lists the breakdown categories despite the lack of an output schema. It could be more explicit about return structure or error handling, but given the low complexity, it is largely complete.

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?

The sole parameter agent_id is already documented in the schema as 'The agent ID' with 100% coverage. The description adds no extra meaning, format requirements, or usage hints beyond the schema, so the baseline score of 3 applies.

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 uses a specific verb 'Get' and clearly identifies the resource as an agent's reputation score with a 0-100 range. It lists distinct breakdown components (tier, endorsements, uptime, age, wishes granted), which sets it apart from siblings like get_agent or get_leaderboard.

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

Usage Guidelines2/5

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

The description offers no guidance on when to use this tool versus alternatives. It does not name related tools like trust_check or get_agent, provide exclusions, or state conditions under which this tool should be preferred.

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