Skip to main content
Glama

Base token / contract safety signals

check_token
Read-only

Use when you need a bounded Base token assessment with explicit unassessed areas. Base contract safety signals from bounded public-chain reads and OFAC. Basic: deployed bytecode and SDN match. Deep adds standard owner(), paused(), totalSupply(), decimals() and ERC-1967 storage observations, exact ERC-1167 minimal-proxy target detection, a Sourcify runtime-verification claim matched to current bytecode, and direct-deployment age when independently supported by the creation receipt. Honeypot/sellability, liquidity locks, holder concentration and scam lists are NOT assessed. Missing data is unknown; never a safe-to-buy verdict. Informational, not financial advice. Basic $0.02; deep $0.05. Shared trial first. Price: 0.02 basic; 0.05 deep USDC. Minimal input example: {"address":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","chain":"eip155:8453","tier":"basic"}. Illustrative output excerpt: {"verdict":"unknown","assessment_complete":false,"unassessed":["honeypot_and_sellability","mint_and_blacklist_privileges","liquidity_lock_or_removability","holder_concentration","non_OFAC_scam_lists","complete_owner_privilege_and_proxy_analysis"]}. Illustrative output excerpt, not a live result, signature, approval or guarantee. Freshness/data/availability checks still apply. How to pay (MCP): First use the existing shared allowance of 3 eligible calls per IP per UTC day, without payment metadata. This is shared with eligible HTTP trials, not a new allowance. Use an x402-capable MCP client. A generic MCP connector without payment support cannot complete a paid continuation. On payment required, STOP. Inspect the exact accepts amount, asset, network and payTo; obtain explicit wallet/budget approval before continuing. Only after approval, let the configured x402 MCP client attach its signed payload in _meta["x402/payment"] and retry the same tools/call arguments. Never send a separate USDC transfer or paste keys into tool arguments. Never silently fall back from free access to payment. If a signed attempt has an unknown outcome, inspect that authorization/transaction; do not create another automatically.

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": "check_token"
  }
}

Input Schema

NameRequiredDescriptionDefault
tierNoOptional. Assessment tier enum string: basic or deep. Example: basic. Defaults to basic; existing prices and incomplete-assessment limits apply.basic
chainNoOptional. CAIP-2 chain identifier string; only Base eip155:8453 is supported. Example: eip155:8453. Defaults to Base when omitted.
addressYesRequired. 0x-prefixed 20-byte Base address string. Example: 0xBf4164e07552e4c1b1B1597E72C7acAA3F0a1c58.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / address / description
      Added value: +"Required. 0x-prefixed 20-byte Base address string. Example: 0xBf4164e07552e4c1b1B1597E72C7acAA3F0a1c58."
    • addedInput schema / properties / chain / description
      Added value: +"Optional. CAIP-2 chain identifier string; only Base eip155:8453 is supported. Example: eip155:8453. Defaults to Base when omitted."
    • addedInput schema / properties / tier / description
      Added value: +"Optional. Assessment tier enum string: basic or deep. Example: basic. Defaults to basic; existing prices and incomplete-assessment limits apply."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: states that missing data resolves to unknown rather than a safe verdict, that no safe-to-buy verdict is produced, that freshness/availability checks apply, and that paid continuation requires explicit approval with an x402 signed payload. It also discloses the exact free tier (3 eligible calls per IP per UTC day, shared with HTTP trials) and the no-silent-fallback rule, which is the key operational risk an agent needs to know.

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?

Front-loaded correctly, with the purpose and unassessed areas before the payment mechanics. However, pricing is restated three times ('Basic $0.02; deep $0.05', 'Price: 0.02 basic; 0.05 deep USDC', plus the enum description), and the payment/retry guidance is padded with repeated warnings that inflate the text considerably for a three-parameter read tool.

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

Completeness5/5

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

With no output schema, the description compensates by supplying an illustrative output excerpt showing verdict, assessment_complete and the unassessed array, plus a minimal input example. Tier capabilities, chain constraint, free-tier limits, payment escalation path and the unknown-data semantics are all covered, which is sufficient for correct invocation.

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 description coverage is already 100%, so the schema documents all three parameters. The description still adds real meaning beyond the enum by stating what 'deep' buys over 'basic' (owner(), paused(), totalSupply(), decimals(), ERC-1967 storage, ERC-1167 proxy target detection, Sourcify claim matching, creation-receipt age) and by attaching prices to each tier, which the schema does not.

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?

States a specific verb and resource ('bounded Base token assessment', 'Base contract safety signals from bounded public-chain reads and OFAC') and enumerates exactly what basic versus deep tiers inspect. It also draws a hard boundary around what is not covered (honeypot/sellability, liquidity locks, holder concentration, scam lists), so an agent can tell this apart from broader security checks in the sibling set.

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?

'Use when you need a bounded Base token assessment with explicit unassessed areas' plus the NOT-assessed list gives clear when-to-use and when-not-to-use signals, and the payment section states the free-trial path and the stop condition on payment-required. It never names a sibling alternative (e.g. security_check or check_payee), so routing between overlapping tools is left to inference.

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.