Skip to main content
Glama

token_dd__sanctions_batch

Token due diligence on Base: contract/owner/proxy facts, privileged-selector scan, sanctions lookup, transfer checks and exit-slippage quotes. Batch and watch paths included. JSON out. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/token-dd/sanctions_batch

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

Input Schema

NameRequiredDescriptionDefault
addrNo
chainNo
size_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well on the operational side: it discloses the paid model ($0.01 per call in USDC on Base, eip155:8453), the x402 payment field location (params._meta['x402/payment']), the JSON output format, and the HTTP endpoint. It stops short of stating read-only semantics, rate limits, or failure behavior, which keeps it from a 5.

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?

It is dense and front-loaded: capability list first, then payment and transport details. Every sentence carries information, though the capability enumeration is long enough to read as a feature dump rather than a focused purpose statement.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and 0% parameter documentation, the description must cover both behavior and parameters. It covers payment and transport well but leaves all three inputs undefined and does not distinguish this tool from its sanctions and batch siblings, so an agent cannot call it confidently.

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

Parameters2/5

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

Schema description coverage is 0% and the description explains none of the three parameters: addr, chain, and size_usd are never mentioned or exemplified. Worse, the description asserts the tool is 'on Base' while a chain parameter exists, and size_usd (presumably input to exit-slippage quotes) is left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description lists concrete capabilities (contract/owner/proxy facts, privileged-selector scan, sanctions lookup, transfer checks, exit-slippage quotes) but presents them as a package rather than stating what this specific tool returns. Since the name is sanctions_batch and siblings token_dd__sanctions and token_dd__batch exist, the description never clarifies what distinguishes this tool from those two, leaving the core identity ambiguous.

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

Usage Guidelines2/5

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

It says 'Batch and watch paths included' but gives no when-to-use criteria, no exclusions, and no pointer to token_dd__sanctions (single) or token_dd__batch as alternatives. An agent still has to guess whether to call this or a sibling for a single-address sanctions screen.

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