Skip to main content
Glama
Sign In

P0 Agent Economy Index

by dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank
OverviewDiscussionsAdmin

Token risk

token_risk
Read-onlyIdempotent

Use for a rule-based risk label on an ERC-20 token before you accept or route it: OFAC SDN match, upgradeable proxy, owner with mint/pause/blacklist (USDC, USDT, WBTC, cbBTC issuer-listed). Returns the exact paid x402 request for your input (GET /token/risk, $0.01 per call), with the response schema and an example; call that URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For a wallet (not a token contract) use wallet_risk. With a P0 access key (header Authorization: Bearer p0k_…, buy one at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/keys/buy?usd=5) this tool makes the paid call itself and returns the data, deducting the listed price.

Input Schema

NameRequiredDescriptionDefault
chainNoChain of the token; default base
addressYesToken contract address (0x + 40 hex)
request_keyNoIdempotency key, echoed back

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request_key
      Added value: +{
+  "description": "Idempotency key, echoed back",
+  "pattern": "^[A-Za-z0-9._:-]{1,64}$",
+  "type": "string"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover read-only/idempotent/open-world, but the description adds substantial context beyond them: it discloses the x402 paid-call model, the $0.01 per-call price, that bad input is refused before any charge, and how the P0 access key path works (deducting the listed price). This is rich operational disclosure an agent needs to invoke correctly.

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?

Purpose and scope are front-loaded, and nearly every clause adds real value (risk dimensions, cost, auth, fallback sibling). It is dense and somewhat run-on, but the information density justifies most of the length.

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?

For a payment-gated tool with no output schema and full param coverage, the description covers everything an agent needs: the paid-request flow, the exact GET endpoint and price, that a response schema and example are returned, error/no-charge behavior, and the access-key variant.

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% and the enum for chain is documented, so the schema already carries the parameter semantics. The description references 'your input' and the request URL but adds no per-parameter detail beyond the schema, so baseline 3 is appropriate.

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+resource ('rule-based risk label on an ERC-20 token') and enumerates the risk dimensions covered (OFAC SDN match, upgradeable proxy, owner with mint/pause/blacklist, issuer-listed examples). It also explicitly distinguishes itself from the sibling wallet_risk.

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

Usage Guidelines5/5

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

Gives a clear when-to-use trigger ('before you accept or route it') and names the alternative explicitly ('For a wallet (not a token contract) use wallet_risk'), which lets an agent route correctly without inference.

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

All P0 Agent Economy Index 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