Kristo Intelligence — Base DeFi Signals (x402)

verify_seller_receiver

Read-onlyIdempotent

Read-only; REQUIRES receiver. Audits ANY receiver's incoming USDC on Base: distinct payers, repeat payers, concentration, probes vs customers. Decides whether a seller is safe to pay. Reports partial/failed, never a zero it did not measure.

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": {
      "receiver": "<receiver>"
    },
    "name": "verify_seller_receiver"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Lookback window in days.
`receiver`	Yes	USDC receiver address to audit. A bare 40-hex address is accepted and checksummed.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value on top: it scopes the data to Base USDC only and, importantly, discloses that results may be partial/failed and are never silently zeroed. It does not quantify latency limits or how partial results are signalled in the payload.

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?

Three short, front-loaded sentences with zero filler; the read-only and required-parameter facts come first, then scope, then the reliability caveat. Nothing is repeated redundantly.

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?

With no output schema, the description carries the burden of describing results and does so by enumerating the audit dimensions and the partial/failed outcome. The only gap is the default/limit behavior of the lookback window, which the schema already covers.

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%, so `receiver` and `days` are already fully documented, and the description only reinforces that any receiver address is acceptable. The `days` lookback window is not mentioned in the description at all, so it adds no meaning beyond the schema.

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?

States a specific verb and resource (audits a receiver's incoming USDC on Base) plus the exact metrics it returns: distinct payers, repeat payers, concentration, probes vs customers. The seller-safety framing distinguishes it cleanly from the market/trading-data siblings.

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

Usage Guidelines4/5

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

The phrase 'Decides whether a seller is safe to pay' gives a clear decision context for invocation, and 'REQUIRES `receiver`' flags the prerequisite. It stops short of naming when-not-to-use conditions or an alternative tool for related questions.

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

All Kristo Intelligence — Base DeFi Signals (x402) tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?