Skip to main content
Glama

Pre-screen an ERC-20 for Gateway registration

gateway_token_eligibility
Read-only

Checks an ERC-20 against Zenith registration criteria, including verified source, non-upgradeability, restricted functions, and a simulated holder transfer, to confirm eligibility before a request.

Instructions

Checks an ERC-20 against Zenith's registration criteria: verified source, deployment transaction, not upgradeable, no fee/burn/reflection/rebase/hook/blocklist functions (bytecode selector scan), and a simulated transfer from a real holder (eth_call with a state override) proving it moves exactly the amount. Prepares what Zenith asks for in a request.

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

Input Schema

NameRequiredDescriptionDefault
addressYesERC-20 token address on Zenith EVM

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only say readOnlyHint and openWorldHint; the description goes further by disclosing the mechanism — a bytecode selector scan and an eth_call with state override simulating a real holder transfer to prove exact value movement. That tells the agent the call does on-chain simulation despite being read-only, which is non-obvious and behaviorally relevant. It omits rate limits, failure modes, and whether a partial pass is possible.

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?

Front-loaded with the verb and the full criteria list in a single dense sentence, followed by a short positioning clause. The enumeration is long but each item is a distinct check the agent may care about, so little is wasted; a bulleted form would have improved scanability slightly.

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?

The tool is read-only with one required parameter and there is no output schema, so the description carries the burden of indicating what comes back — yet it never says whether the result is a boolean, a per-criterion checklist, or reasons for failure. Given that the whole point is a pass/fail screen, that gap matters for an agent deciding what to do with the response.

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

Parameters3/5

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

Schema coverage is 100% with the address already documented as 'ERC-20 token address on Zenith EVM', so the baseline of 3 applies. The description confirms the input is an ERC-20 but adds no format, checksum, or chain nuance beyond the schema.

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?

Names a specific verb and resource ('Checks an ERC-20 against Zenith's registration criteria') and enumerates the actual criteria: verified source, deployment tx, non-upgradeable, banned selector classes, and a simulated transfer. That is far beyond a restatement of the title. It does not, however, distinguish itself from plausible siblings such as gateway_preflight or zenith_check_compat, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

'Prepares what Zenith asks for in a request' implies this is a pre-registration screen, which is useful positioning. But there is no explicit when-to-use statement, no when-not (e.g. already-registered tokens, non-ERC-20 addresses), and no named alternative for agents who want a cheaper or different compatibility check.

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