Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

agent_reputation_mesh

[$0.05] Score any EVM counterparty or agent wallet across Base L2 on-chain nonce/balance history, whale activity, x402 settlement reliability, and 48h security flags.

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": "agent_reputation_mesh"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoTarget chain ('base' or 'ethereum')base
addressNoEVM wallet or contract address (0x...)
timeout_msNoOptional deadline in ms. If the local LLM would exceed it, the response comes back fast with "degraded": true and non-LLM/cached data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does disclose the price ([$0.05]) and the signals inspected, but says nothing about read-only nature, required payment/auth setup for x402, rate limits, caching, or what a 'score' actually looks like numerically. The degraded-response behavior is documented only in the timeout_ms parameter, not in the description.

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 zero filler; the cost marker comes first and the substantive scope follows immediately. Nothing is repeated or padded.

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 paid reputation-scoring tool with no output schema and no annotations, the description should say more about what comes back (numeric score, band, per-signal breakdown) and about the payment flow implied by [$0.05]. It covers inputs and data sources adequately but leaves the return contract and cost mechanics underspecified.

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%, so all three parameters are already documented, giving a baseline of 3. The description adds no per-parameter meaning and in fact its "Base L2" phrasing sits in tension with the chain parameter's 'ethereum' option.

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 uses a specific verb ("Score") on a specific resource ("any EVM counterparty or agent wallet") and enumerates the data sources feeding the score (nonce/balance history, whale activity, x402 settlement reliability, 48h security flags). This is clearly distinguishable from siblings like crypto_whale_flows or crypto_exploit_radar, which measure single signals rather than producing a composite reputation score. It falls short of a 5 because the stated scope ("Base L2") conflicts with the schema's allowance of 'ethereum', leaving the actual coverage slightly ambiguous.

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?

"Score any EVM counterparty or agent wallet" implies the use case (vetting a counterparty before transacting or settling via x402), but there is no explicit when-to-use framing, no exclusions, and no routing to alternatives such as agent_preflight, security_preflight_402, or crypto_exploit_radar. Usage is inferable rather than stated.

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