Skip to main content
Glama

Pre-trade token risk check (honeypot, taxes, owner powers)

check_token
Read-only

Before buying or accepting a token: simulates a buy and sell on the deepest pool (Uniswap V2/V3/V4 + Aerodrome on Base, Uniswap V2/V3/V4 on Ethereum) to detect honeypots and taxes, and checks owner powers (mint/pause/blacklist/fees), upgradeable proxy, liquidity and sanctioned owner. Verdict avoid/caution/ok with a signed receipt. $0.01 per call after the free daily quota.

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
chainNoDefault base. Buy/sell simulation on base and ethereum.
addressYesToken contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description explains the simulation method, supported pools and chains, owner-power checks, verdict categories, signed receipt, and per-call cost after a free quota. It discloses enough non-obvious behavior for an agent to understand the call's depth and cost.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the when-to-use case and then packs the simulation scope, checks, verdict output, and pricing into two efficient sentences. There is little wasted wording.

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?

For a complex cross-chain token risk check with no output schema, the description covers what is checked and the verdict categories returned. It does not detail the receipt contents or all verdict evidence, but an agent has enough context to call it correctly.

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%, so the input schema already documents the address and chain parameters. The description repeats that buy/sell simulation applies on Base and Ethereum but adds little parameter-level meaning beyond the schema description.

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?

The description states a specific verb and resource: it simulates buy/sell transactions and checks owner powers to assess token risk before purchase. This is clearly distinct from the sibling tools check_payment_counterparty and verify_receipt, which concern payment counterparties and receipt verification.

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 gives an explicit trigger: 'Before buying or accepting a token.' It does not describe when not to use it or name alternative tools, but the intended context is clear.

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