P0: sanctions, KYB and payee checks

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

Sanctions screening batch

sanctions_screening_batch

Read-onlyIdempotent

Use when you need to screen a list of wallet addresses against sanctions lists in one call: up to 25 per POST (0x, BTC, TRX, SOL and any other 20-128 character address). Returns the paid x402 request for your input (POST /sanctions/check/batch, $0.125 per call; schema linked). POST that JSON body to the URL with an x402 or MPP client to get the data. Bad input is refused before any charge. For one address or a name use sanctions_screening. With an access key (Authorization: Bearer p0k_..., buy at https://x402-bazaar-rank.x402-bazaar-rank-worker.workers.dev/keys/buy?usd=5) the tool pays the call itself, returns the data and deducts the price.

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": {
      "addresses": "<addresses>"
    },
    "name": "sanctions_screening_batch"
  }
}

Input Schema

Name	Required	Description	Default
`addresses`	Yes	1 to 25 crypto addresses to screen (as written on their chains); duplicates are removed; names are not accepted

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only say readOnly/idempotent/openWorld, but the description goes much further: it discloses the two-step x402 flow (this tool returns a request body, not the data), the price ($0.125 per call), the endpoint, and the Bearer-key mode that makes the tool pay and return data directly. That is exactly the behavioral context an agent needs before incurring cost.

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?

Front-loaded with the use condition and the differentiator, then the mechanics. It is dense and information-rich, though the parenthetical price/endpoint cluster and the long access-key URL make the middle sentences heavier than necessary.

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 correctly explains that the return value is a payable request object and how to convert it into data, resolving the biggest ambiguity. It stops short of describing what the eventual screening payload contains, which is the only remaining gap for a paid two-step tool.

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

Parameters4/5

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

Schema coverage is 100% and already documents min/max items, length bounds, and duplicate removal. The description adds meaning beyond the schema by naming accepted chain formats (0x, BTC, TRX, SOL) and generalizing to any 20-128 character address, so it earns a point above baseline.

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 ('screen a list of wallet addresses against sanctions lists in one call') plus the concrete limit (up to 25 per POST). It explicitly distinguishes itself from the sibling sanctions_screening by naming the single-address/name case as the other tool's job.

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?

Opens with an explicit 'Use when you need to screen a list' condition and routes the alternative case ('For one address or a name use sanctions_screening') to the correct sibling. It also flags that bad input is refused before any charge, which tells the agent it is safe to attempt.

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

All P0: sanctions, KYB and payee checks 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.

Resources

Need Help?