Skip to main content
Glama

get_agent_reputation

get_agent_reputation

Read a seller's completed, disputed and refunded order counts and volume.

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": {
      "address": "<address>"
    },
    "name": "get_agent_reputation"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesSeller wallet address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description must carry the behavioral burden. 'Read' implies a non-mutating lookup and the enumeration of completed/disputed/refunded metrics discloses what the result contains, but nothing is said about behavior for unknown or non-seller addresses, rate limits, or data freshness.

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?

A single front-loaded sentence with no filler; the metrics are enumerated compactly and nothing could be removed without losing information.

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

Completeness3/5

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

For a one-parameter read tool this is close to sufficient, and it sketches the returned metrics, which partly compensates for the absent output schema. However, with no annotations and no output schema, it does not resolve units/currency of 'volume' or behavior on a bad address, leaving real gaps.

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% and the schema already labels 'address' as a 'Seller wallet address.' The description's phrase 'a seller's ...' is consistent with that but adds no new semantics such as accepted address formats or chain scoping, so the baseline applies.

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?

The description gives a specific verb ('Read') and a specific resource ('a seller's completed, disputed and refunded order counts and volume'), so an agent knows exactly what data comes back. It does not explicitly distinguish itself from lookalike siblings such as get_track_record or get_activity, which keeps it out of the top band.

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?

There is no guidance on when to call this versus alternatives, no prerequisites, and no stated conditions (e.g., use before accepting a commerce quote or engaging an agent). The reader must infer usage from the purpose sentence 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