Skip to main content
Glama
Sign In

ARP

by io.github.Wieedze
OverviewDiscussionsAdmin

arp_tool_reputation

Who declared using one tool, and how strongly. Returns each declaration with the agent that made it, the amount behind it and the amount against it, plus totals. Read an amount with how many supports make it up: one large amount can come from a single account.

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": {
      "tool_atom_id": "<tool_atom_id>"
    },
    "name": "arp_tool_reputation"
  }
}

Input Schema

NameRequiredDescriptionDefault
attested_byNoOptional. Keep only declarations this account backs. A filter, never a claim that nobody else does (ADR 0034).
tool_atom_idYesThe `atom_id` from `arp_pulse`, or, where `arp_find_tools` is served, a tool's `id` (`tool_atom_id` in its full detail). 0x + 32 bytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the return shape (each declaration with the declaring agent, amount behind, amount against, plus totals) and an important interpretive caveat that a single large amount may come from one account. It omits read-only confirmation, pagination, and ordering, leaving real gaps for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core question and the result shape. The final sentence is slightly awkward ('Read an amount with how many supports make it up') but earns its place as interpretive guidance.

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 two-parameter read tool with no output schema, the description should explain what comes back; it partially does (declarations, agent, for/against amounts, totals) but leaves pagination, ordering, and empty-result behavior unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description says nothing about tool_atom_id or the attested_by filter; the only hint is the interpretive sentence about counting supports, which does not map explicitly to the filter parameter.

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?

States a specific verb+resource: it returns the declarations (attestations) that some agent made about using a given tool, along with strength. That distinguishes it from arp_pulse and arp_agent_endpoints by resource, though it never names a sibling to sharpen the contrast.

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?

Usage is only implied by the opening question ('who declared using one tool, and how strongly'), which suggests a per-tool reputation lookup. There is no explicit when-to-use vs when-not, and no statement of prerequisites or alternatives.

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

All ARP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources