Skip to main content
Glama

token_dd__sanctions

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

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

Input Schema

NameRequiredDescriptionDefault
addrNo
chainNo
size_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior3/5

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

With no annotations, the description still discloses genuinely useful behavior: JSON output, an HTTP GET endpoint, and a mandatory $0.01 USDC payment on Base via x402 in params._meta["x402/payment"]. That payment/auth requirement is the kind of context annotations would otherwise supply. It does not say whether the call is read-only, what happens on payment failure, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Compact, with pricing and endpoint front-loaded in fragments rather than buried. However, the opening capability list is a dense dump that spends attention on features that may belong to sibling tools, so not every sentence earns its place for this specific tool.

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 3-parameter tool with no annotations, no output schema, and no parameter descriptions, the definition should clarify inputs, expected result shape, and how it differs from the many adjacent sanctions/DD siblings. It covers payment and transport but leaves the actual call semantics underdetermined.

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% for addr, chain, and size_usd, and the description adds no meaning for any of them. Worse, it says the tool operates 'on Base' while a free-form chain parameter exists, leaving the agent unsure whether chain is required or ignored, and size_usd is never tied to the mentioned slippage quotes.

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 name says 'sanctions' and the endpoint is /token-dd/sanctions, but the description enumerates a whole due-diligence suite (contract/owner/proxy facts, privileged-selector scan, transfer checks, exit-slippage quotes). It is unclear whether this call performs sanctions screening specifically or all of those checks, which blurs the verb+resource and makes it hard to distinguish from siblings like token_dd__check or check_sanctions__token.

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?

No statement of when to use this versus token_dd__sanctions_batch, token_dd__watch, or token_dd__check. The line 'Batch and watch paths included' actually muddies routing because dedicated batch and watch siblings exist. There are no exclusions or prerequisites beyond the payment note.

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