Skip to main content
Glama

Trading Signals Toolkit

Base Token Verdict

token_verdict
Read-only

Call before an agent buys, swaps into, lists or accepts a Base ERC-20. Returns safe / caution / avoid plus an A-F grade with plain reasons: buy-then-sell honeypot simulation with taxes, owner, mint, proxy, blacklist, pause and tax-change flags, liquidity across DEXes and LP lock, top-10 holder concentration, launch-window snipers and same-block bundles, and the deployer. Not a security audit. Read-only, never places orders. Informational only, not investment advice.

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_verdict"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesBase ERC-20 token contract address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the bar is lower, yet the description still adds real behavioral context: buy-then-sell honeypot simulation with taxes, liquidity/LP-lock checks, holder concentration, sniper and bundle detection. It explicitly states it never places orders and is not an audit, which tells the agent how to weight the result. It stops short of disclosing latency, caching, or failure modes for unverified or non-token addresses.

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?

The trigger condition is front-loaded in the first clause, followed by outputs and then the checked signals, so an agent gets the decision-relevant information immediately. The closing disclaimers ("Not a security audit", "Read-only, never places orders", "Informational only, not investment advice") overlap somewhat with each other and with the readOnly annotation, costing a point.

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 carries the full burden of explaining return values, and it does: verdict taxonomy, A-F grade, plain reasons, and the specific risk categories evaluated. For a single-parameter read-only tool, an agent has everything needed to decide to call it and interpret 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?

There is a single parameter and the schema already documents it at 100% coverage, including a 0x-address regex and the 'Base ERC-20 token contract address' meaning. The description repeats the resource type ('Base ERC-20') but adds no new semantics such as behavior on wrong-chain or non-contract addresses, so the baseline 3 applies.

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 opens with a specific verb+resource and scope: vetting a Base ERC-20 before buying, swapping, listing or accepting it. It then enumerates the verdict outputs (safe / caution / avoid, A-F grade) and the concrete signals checked, which separates it from chain-variant or generic pre-trade siblings without naming them.

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?

"Call before an agent buys, swaps into, lists or accepts" gives an explicit trigger condition tied to real agent actions, which is stronger than typical implied usage. It also sets a boundary ("Not a security audit", "Informational only, not investment advice") but never points to an alternative tool when a deeper audit or a cross-chain check is needed.

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