Skip to main content
Glama

edge-signals

token_risk_before_buy

Before buying or approving an ERC20: honeypot / token-risk check (GoPlus). Returns verdict avoid|caution|ok and risk flags.

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

Input Schema

NameRequiredDescriptionDefault
chainNobase (default), ethereum, bsc, arbitrum, optimism, polygon
addressYesERC20 contract

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add real value by naming the data source (GoPlus) and the output verdict vocabulary, but it omits whether the call is read-only, what happens for an unlisted chain or a non-contract address, and whether the check can miss novel honeypots.

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?

A single compact sentence, front-loaded with the trigger condition, then the mechanism, then the return values. No filler and nothing that could be cut without losing information.

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 two-parameter read check with no output schema, the description supplies the essential pieces: when to call it, what engine backs it, and what the agent gets back. The remaining gaps are about failure modes and unlisted chains rather than about how to call the tool 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 both parameters are already documented, including the chain enum values and the default of base. The description only echoes the ERC20 contract concept and adds no syntax, casing, or address-format guidance 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?

States a specific verb-and-resource: a honeypot/token-risk check (GoPlus) run on an ERC20 before buying or approving. It also names the return shape (verdict avoid|caution|ok plus risk flags). It does not differentiate itself from the sibling token_verdict_before_buy, whose name suggests a near-identical function, leaving genuine ambiguity.

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?

Gives clear trigger context in the leading phrase: run this before buying or before approving an ERC20. There are no when-not conditions, no prerequisites, and no explicit pointer to the similar sibling tool, so the agent must infer which of the two verdict tools applies.

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