Skip to main content
Glama

token_dd__check

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/check

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

Input Schema

NameRequiredDescriptionDefault
addrNo
chainNo
size_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  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. Changed2 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"0x-prefixed 40-hex token contract address"
    • addedInput schema / properties / chain / description
      Added value: +"Chain id, e.g. base"
  5. Changed2 schema fields changed
    • removedInput schema / properties / address / description
      Removed value: -"0x + 40 hex token contract address"
    • removedInput schema / properties / chain / description
      Removed value: -"one of base, ethereum, bsc, arbitrum"
  6. Changed3 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"Token contract address"New value: +"0x + 40 hex token contract address"
    • changedInput schema / properties / chain / description
      Previous value: -"Chain id, e.g. base"New value: +"one of base, ethereum, bsc, arbitrum"
    • changedInput schema / required
      Previous value: -[
      -  "address"
      -]New value: +[
      +  "chain",
      +  "address"
      +]
  7. Changed3 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Token contract address"
    • addedInput schema / properties / chain / description
      Added value: +"Chain id, e.g. base"
    • addedInput schema / required
      Added value: +[
      +  "address"
      +]
  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.2/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 disclose significant operational behavior: it is a paid call ($0.01 USDC on eip155:8453), payment is threaded via x402 in params._meta, transport is an HTTP GET, and output is JSON. Gaps remain around failure modes (what happens if payment is absent), rate limits, and whether the checks are read-only, 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?

The capability list is front-loaded and the pricing/transport details are packed into the closing sentences with no filler. The only wasted line is 'Batch and watch paths included', which adds ambiguity rather than information.

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?

Pricing, payment mechanism, transport and the set of checks are covered, which is substantial for a tool with no annotations and no output schema. However, three totally undocumented parameters on a multi-capability tool mean the definition is not yet complete enough for confident invocation.

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% across three parameters, so the description must compensate and largely does not: addr and chain are never mentioned, and size_usd is only obliquely implied by 'exit-slippage quotes'. An agent must guess that addr is the token address, that chain defaults to Base, and that size_usd sizes the slippage quote.

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+resource ('Token due diligence on Base') and enumerates concrete checks: contract/owner/proxy facts, privileged-selector scan, sanctions lookup, transfer checks and exit-slippage quotes. That is far more than a restatement of the name. It stops short of 5 because it never distinguishes itself from the many near-siblings (token_dd__verify, token_dd__sanctions, token_dd__tx), so an agent still cannot tell which one to reach for.

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 or when-not-to-use guidance and no named alternative. The line 'Batch and watch paths included' is actively unhelpful for routing, since token_dd__batch and token_dd__watch exist as separate siblings, leaving the agent unsure whether this tool or those should be called.

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