Skip to main content
Glama

token_dd__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/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__batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
addrNo
chainNo
size_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / addr
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / chain
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / size_usd
      Added value: +{
      +  "type": "number"
      +}
    • removedInput schema / properties / tokens
      Removed value: -{
      -  "type": "string"
      -}
  2. Changed4 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
      -  "description": "Token contract address, 0x + 40 hex",
      -  "type": "string"
      -}
    • removedInput schema / properties / chain
      Removed value: -{
      -  "description": "Chain: base, ethereum, etc.",
      -  "type": "string"
      -}
    • addedInput schema / properties / tokens
      Added value: +{
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "address"
      -]
  3. Changed3 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"0x-prefixed 40-hex token contract address"New value: +"Token contract address, 0x + 40 hex"
    • changedInput schema / properties / chain / description
      Previous value: -"Chain id, e.g. base"New value: +"Chain: base, ethereum, etc."
    • changedInput schema / required
      Previous value: -[
      -  "chain",
      -  "address"
      -]New value: +[
      +  "address"
      +]
  4. Added
  5. Removed
  6. Changed1 schema field changed
    • changedInput schema / properties / tokens / description
      Previous value: -"Comma-separated chain:address pairs"New value: +"comma-separated chain:address pairs, up to 10"
  7. Changed4 schema fields changed
    • removedInput schema / properties / address
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / chain
      Removed value: -{
      -  "type": "string"
      -}
    • addedInput schema / properties / tokens
      Added value: +{
      +  "description": "Comma-separated chain:address pairs",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "tokens"
      +]
  8. Changed4 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"Token contract address, 0x-prefixed 40 hex chars"
    • removedInput schema / properties / chain / description
      Removed value: -"base, ethereum, arbitrum, optimism or polygon"
    • removedInput schema / properties / token
      Removed value: -{
      -  "description": "Alias for address",
      -  "type": "string"
      -}
    • removedInput schema / required
      Removed value: -[
      -  "chain",
      -  "address"
      -]
  9. Changed4 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"0x-prefixed token contract address"New value: +"Token contract address, 0x-prefixed 40 hex chars"
    • addedInput schema / properties / chain / description
      Added value: +"base, ethereum, arbitrum, optimism or polygon"
    • removedInput schema / properties / chain / enum
      Removed value: -[
      -  "base",
      -  "ethereum",
      -  "bsc",
      -  "arbitrum"
      -]
    • addedInput schema / properties / token
      Added value: +{
      +  "description": "Alias for address",
      +  "type": "string"
      +}
  10. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well on the operational side: it discloses JSON output, a fixed price ($0.01 per call in USDC on Base, eip155:8453), and the exact payment mechanism (x402 via params._meta['x402/payment']) plus the HTTP endpoint. It stops short of stating failure modes, rate limits, or what a batch run returns, which is why it is not 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.

Conciseness5/5

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

Purpose is front-loaded in the first clause, followed by capability list, then operational facts (output format, price, payment, endpoint). Every sentence contributes; the vague 'Batch and watch paths included' is the only soft spot but costs little.

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

Completeness3/5

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

No annotations, no output schema, and three fully undocumented parameters mean the description should be doing more. It covers cost, payment, transport and output format well, but says nothing about what each parameter does or what a batch response contains, so an agent can pay for and call it yet may populate addr/chain/size_usd incorrectly.

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 all three params (addr, chain, size_usd) and the description explains none of them. It even implies 'on Base' is fixed while a chain parameter exists, leaving their relationship ambiguous. The only param value added is the undocumented payment field in _meta, which does not compensate for the rest.

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

Purpose4/5

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

The description names a specific verb and resource ('Token due diligence on Base') and enumerates the concrete checks performed: contract/owner/proxy facts, privileged-selector scan, sanctions lookup, transfer checks, exit-slippage quotes. It does not distinguish this batch variant from its obvious siblings (token_dd__check, token_dd__sanctions_batch, token_dd__txbatch), so an agent cannot tell from the text alone when the batch form is the right pick.

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?

There is no when-to-use / when-not guidance. 'Batch and watch paths included' gestures at capability but never says what 'batch' means here (multiple addresses? a queued job?) or why an agent would choose this over token_dd__check. No prerequisites or exclusions are stated.

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