agentshield-mcp

get_reputation

Check an AI agent's reputation score and tier (NEW, ACTIVE, VERIFIED, TRUSTED) to assess its trust level. Higher tiers unlock more benefits.

Instructions

Get an agent's reputation score and tier (NEW, ACTIVE, VERIFIED, TRUSTED). Higher reputation = more benefits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_reputation"
  }
}

Input Schema

Name	Required	Description	Default
`agent`	No	Agent API key prefix (optional, defaults to your key)
`api_key`	No	Your API key

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Aug 10, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states that higher reputation means more benefits, but does not describe operational traits such as whether it is a read-only operation, authentication requirements, or rate limits.

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 with a parenthetical tier list, making it extremely concise and front-loaded. Every word contributes to defining the tool's purpose without redundancy.

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 getter with two optional parameters, the description adequately conveys the return value (score and tier) and the meaning of tiers. Although no output schema exists, the tier list provides sufficient context for typical use cases.

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 coverage is 100% with both parameters (agent and api_key) already described in the input schema. The description adds no additional parameter semantics, so the baseline 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 clearly states the tool retrieves an agent's reputation score and tier, listing the specific tier values (NEW, ACTIVE, VERIFIED, TRUSTED). This specific verb+resource combination distinguishes it from sibling tools like get_stats and 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 provides no guidance on when to use this tool versus alternatives. It neither mentions alternative reputation-related tools nor any 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.