Skip to main content
Glama

token_dd__exit

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

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

Input Schema

NameRequiredDescriptionDefault
addrNo
chainNo
size_usdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real behavioral value: cost ($0.01 per call in USDC on Base), the x402 payment location in params._meta, the transport (HTTP GET) and JSON output. It still omits whether the call is read-only, what happens with missing addr/chain (Base appears hardcoded yet chain is a parameter), and error/failure behavior.

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?

Capability list is front-loaded and each element (price, payment mechanism, output format, endpoint) is arguably useful, but the single run-on enumeration sentence pushes the tool's distinctive "exit" purpose into a trailing clause. It is dense rather than bloated, though the raw HTTP URL and payment details intrude before the agent learns what makes this tool unique.

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?

For a 3-parameter tool with no output schema and no annotations, the description covers cost, payment, transport, and output format, which is substantial. It falls short on parameter meaning and on sibling differentiation, which are the two things an agent most needs here.

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 coverage is 0%, so the description must explain addr, chain, and size_usd itself. It only hints indirectly: "on Base" suggests chain, and "exit-slippage quotes" suggests size_usd is the position size driving the quote, but neither is stated explicitly, and addr is never tied to the contract address or wallet being checked.

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 does name a specific verb and resource ("Token due diligence on Base") and enumerates concrete checks: contract/owner/proxy facts, privileged-selector scan, sanctions, transfer checks, exit-slippage quotes. But the enumerated scope overlaps almost entirely with siblings like token_dd__check and token_dd__sanctions, and nothing explains why this specific tool is called "exit" rather than a general check. An agent can tell it does token due diligence but not how it differs from its near-identical siblings.

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?

"Batch and watch paths included" alludes to alternatives but does not say when to prefer this tool over token_dd__batch or token_dd__watch, nor when to use exit quotes versus the plain check. There is no explicit when-to-use, when-not-to-use, or prerequisite guidance; the agent must infer from the name.

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