Skip to main content
Glama
Sign In

automaton

by uk.firstmention.api
OverviewDiscussionsAdmin

token_dd__watch

One-call token due diligence for Base/Ethereum tokens: DexScreener markets + GoPlus security/holders + chain RPC, joined and scored. Free /preview teaser. 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/watch

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "address": "<address>"
    },
    "name": "token_dd__watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain: base, ethereum, etc.
addressYesToken contract address, 0x + 40 hex

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. Changed4 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
+  "description": "0x-prefixed 40-hex token contract address",
+  "type": "string"
+}
    • addedInput schema / properties / chain
      Added value: +{
+  "description": "Chain id, e.g. base",
+  "type": "string"
+}
    • removedInput schema / properties / tokens
      Removed value: -{
-  "description": "Comma-separated chain:0xaddress pairs, max 10",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "tokens"
-]New value: +[
+  "chain",
+  "address"
+]
  3. Added

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does add real behavioral detail the schema cannot express: the aggregation sources, a free preview tier, a $0.01 USDC-on-Base cost, and the x402 payment handshake. What it omits is more consequential — whether the call is read-only or registers a persistent watcher, whether results are cached, and what happens when a source (GoPlus/DexScreener) fails for a given token.

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?

Three dense sentences, front-loaded with what the tool returns and followed by cost and transport details; nothing is padded. The style is terse and jargon-heavy (x402, eip155:8453) but every clause carries information an agent needs.

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 two-parameter tool with no output schema and no annotations, the description covers data provenance, price, payment mechanism, and endpoint. It still leaves the core ambiguity of 'watch' unresolved and gives no hint of the scored response shape or failure modes, which matters more here than for a simple lookup.

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

Parameters4/5

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

Schema coverage is 100%, so the two declared parameters are already documented and a baseline 3 would apply. The description goes beyond that by documenting an out-of-band parameter not present in the schema at all — params._meta["x402/payment"] with the required network eip155:8453 — which an agent would otherwise be unable to supply.

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 names a concrete verb-and-resource ('token due diligence') and enumerates the three data sources joined into the result, which is genuinely informative. However, it never explains what the 'watch' suffix means here (one-off scored snapshot vs. registering a recurring monitor), and it does not distinguish this from near siblings such as token_dd__check, token_dd__verify, or basedue__watch. An agent can tell it is a token risk lookup but not why it should pick watch over check.

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, no prerequisites beyond payment, and no routing to alternatives among the many token-risk siblings. The pricing and 'free /preview teaser' note gives commercial context but not selection criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All automaton toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources