TWZRD Agent Intelligence

get_top_intel_agents

Read-onlyIdempotent

Leaderboard of observed payer wallets in the x402 settlement graph, each
with its intel score. This is behavioral corpus research, not identity
proof or evidence that the wallet is a TWZRD customer.

Ranks by the wash-discounted effective_score (single-counterparty fleets are
demoted, not hidden) with a deterministic tiebreaker. Set min_paid_calls to
suppress one-shot wallets and max_days_since_last to suppress dormant ones.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of ranked payer wallets to return (default 10).
`min_paid_calls`	No	Filter out wallets with fewer than this many observed paid calls (default 0 = no filter). Use to get credible active counterparties, not a raw dump.
`max_days_since_last`	No	Only include wallets active within this many days (default null = no recency filter). Use e.g. 14 to exclude dormant or historical payers.

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No	Number of rows returned.
`error`	No	Present only on the degraded path.
`agents`	No	Ranked agent rows, each with intel_score, effective_score, wash fields, and rank.
`score_model`	No	Self-describing scoring contract.
`score_version`	No	Scoring contract version.
`data_available`	No	False when the corpus/DB was unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 22, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum number of ranked agents to return (default 10)."New value: +"Maximum number of ranked payer wallets to return (default 10)."

changedInput schema / properties / max_days_since_last / description

Previous value: -"Only include wallets active within this many days (default null = no recency filter). Use e.g. 14 to get a feed of currently-active agents and exclude dormant/historical payers."New value: +"Only include wallets active within this many days (default null = no recency filter). Use e.g. 14 to exclude dormant or historical payers."

First observedJul 11, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes beyond annotations (readOnlyHint, idempotentHint) by explaining the ranking mechanism: 'Ranks by the wash-discounted effective_score (single-counterparty fleets are demoted, not hidden).' This reveals important behavioral context for interpreting results.

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 concise (three sentences), front-loads the main purpose, and avoids extraneous information.

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

Completeness5/5

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

Given the tool's simplicity (3 optional parameters, output schema exists), the description covers purpose, ranking logic, parameter intent, and a disclaimer about the data's nature. It is complete for effective usage.

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 baseline is 3. The description's parameter guidance ('suppress one-shot wallets', 'suppress dormant ones') largely repeats the schema descriptions, adding minimal new value.

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 it returns a 'Leaderboard of observed payer wallets in the x402 settlement graph, each with its intel score.' This distinguishes it from sibling tools like score_wallet_for_intel (single wallet) and get_counterparties (different aspect).

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 description provides guidance on parameter usage: 'Set min_paid_calls to suppress one-shot wallets and max_days_since_last to suppress dormant ones.' It also includes a disclaimer about the nature of the data. However, it does not explicitly state when to use this tool versus alternatives like score_wallet_for_intel.

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

All TWZRD Agent Intelligence tools Inspect

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.