Skip to main content
Glama

Blazar Polygon plugin

Token safety check (honeypot, tax, verified list)

blazar_token_safety
Read-onlyIdempotent

Check a token on Polygon (default), Base or Ethereum (chain param) before trading it: verified-list status (curated list, KyberSwap verified list), KyberSwap honeypot / fee-on-transfer flags, EIP-1967 upgradeable proxy, a simulated transfer that measures the real transfer tax, and for unknown tokens a simulated SELL back to USDC that catches blocked-sell honeypots. Returns verdict ok / caution / blocked with each check. Heuristics only; read-only, nothing is signed.

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": {
      "token": "<token>"
    },
    "name": "blazar_token_safety"
  }
}

Input Schema

NameRequiredDescriptionDefault
deepNoRun the sell simulation for unverified tokens (default true; 2 aggregator calls).
chainNoChain: "polygon" (default, chain 137), "base" (8453) or "ethereum" (1). BZB / BlazarSwap tools are Polygon only.
tokenYesToken to check: a symbol (USDC, WETH, AAVE, LINK...; resolved only via the chain's curated list or an exact unique KyberSwap-verified match) or any 0x token address on the chosen chain. Native coin: "POL" on Polygon, "ETH" on Base / Ethereum.
amountNoTest size in HUMAN units for the simulations. Default 1 token.

Output Schema

NameRequiredDescriptionDefault
noteNo
chainNo
tokenNo
checksNo
chainIdNo
summaryNo
verdictNo
verifiedNo
transferTaxBpsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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, and the description reinforces that with 'read-only, nothing is signed', while adding genuinely new behavior: the verdict taxonomy (ok / caution / blocked), the use of real simulations versus static flags, and the admission that results are heuristic. It does not discuss latency or the cost of deep mode, which the schema carries instead.

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?

One dense sentence front-loads the purpose, then enumerates checks in priority order and closes with the verdict contract and the read-only caveat. Nothing is redundant, though the middle clause list is long enough that an agent may skim past the output format.

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 read-only, multi-chain diagnostic with four parameters and an output schema, the definition covers scope, defaults, chain limitations, check inventory, and the heuristics caveat. The only omissions are operational details (call cost, response time), which are partly covered by the schema's note about two aggregator calls.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by tying the parameters to intent, explaining that the simulations exist to measure real tax and catch blocked-sell honeypots on unknown tokens, which gives the agent a reason to choose deep/amount values. It still does not elaborate the symbol-vs-address resolution rules, which live only in the schema.

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 and resource ('Check a token on Polygon..., Base or Ethereum') and then enumerates the exact checks performed: verified-list status, honeypot/fee-on-transfer flags, EIP-1967 proxy, simulated transfer tax, and a simulated SELL. No sibling tool in the list is a token safety checker, so the agent can distinguish this immediately.

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 a clear trigger context ('before trading it') and explains that the sell simulation is scoped to unknown tokens, which tells the agent the intended workflow position. It does not explicitly name an alternative tool or state when a result should be disregarded beyond the 'heuristics only' caveat, so it stops short of a 5.

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