Skip to main content
Glama

token-check

Returns a fact summary of a Base token: name, symbol, decimals, total supply, proxy/upgradeable status, owner and whether ownership is renounced, which risky functions exist in the contract code (mint, pause, blacklist, fee setters, ownership transfer), and the token's deepest DEX pools on Base (Uniswap v2/v3, Aerodrome) with reserves, USD price and liquidity. Fields: ok, token, abilities, market.deepest_pool, market.pools, risk_flags, grade (A-F), summary, warnings, checked_at, block. Grade rule: starts at 100; each risk flag subtracts points (mint, pause, blacklist, proxy, privileged owner -25; fee setters, owner transfer -10; under $10,000 liquidity -20; no liquidity -40); renounced owner adds 10. A 85+, B 70+, C 55+, D 40+, F below. Stablecoins like USDC are upgradeable by their issuer, so they lose points. Data summary from on-chain code and pool reserves, not financial advice. Base only. Input: ?address=0x... (token contract). Cached 60 seconds. Free: 3 calls a day per visitor; a

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>",
      "chain": "<chain>"
    },
    "name": "token-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYese.g. base
addressYese.g. 0x4200000000000000000000000000000000000006

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/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 so richly: it discloses the caching window (60 seconds), the rate limit (3 calls/day per visitor), the data provenance ('from on-chain code and pool reserves'), and the grading methodology with exact point deductions. It also volunteers a non-obvious caveat that stablecoins like USDC lose points for issuer upgradeability, which prevents a misread of the grade.

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?

Purpose is front-loaded, but the body is one dense run-on that mixes return-field inventory, a full grade arithmetic rubric, provenance, caching, and pricing. The rubric ('mint, pause, blacklist... -25; fee setters... -10') is more detail than an agent needs to select the tool, and the text terminates mid-sentence ('Free: 3 calls a day per visitor; a'), signaling truncation that undercuts the structure.

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

Completeness4/5

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

Because there is no output schema, enumerating the returned fields (ok, token, abilities, market.deepest_pool, market.pools, risk_flags, grade, summary, warnings, checked_at, block) is genuinely load-bearing and it is done. Complexity is high and largely covered, though the truncated final clause leaves the pricing/rate-limit picture incomplete.

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 baseline is 3, but the description adds real meaning beyond the schema: it clarifies that address is the token contract (not a wallet or pool) and reinforces that chain is effectively constrained to Base. That disambiguation is useful because the schema's generic 'e.g. base' hint does not convey the restriction.

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

Purpose5/5

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

Opens with a specific verb+resource: 'Returns a fact summary of a Base token,' then enumerates exactly which facts (name, symbol, decimals, supply, proxy status, owner, risky functions, DEX pools with reserves/price/liquidity). This is unmistakably distinct from every sibling (json-check, slugify, page-to-markdown, etc.), which are unrelated utilities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states hard scoping and constraints — 'Base only', the address must be a token contract rather than a wallet, 'not financial advice', 60s cache, and a free tier of 3 calls/day. There is no explicit when-not-to-use or named alternative, but the scope statements are strong enough that an agent knows the boundary of applicability.

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