Skip to main content
Glama

APEX Agent Safety & Guardrails

Token safety check

token_safety_check
Read-onlyIdempotent

Is this token safe to buy? Give a token contract address and a chain (base, arc, robinhood, solana or x1) and get a verdict: BASED, MID, COOKED or RADIOACTIVE, from a real simulated buy and full sell (Base, Robinhood Chain) or that chain's measured exit (Arc, Solana, X1), with the round-trip cost and a plain one-liner. Free, read-only, no account. It measures the exit right now; it is not advice and not a guarantee, and a read we could not make comes back as an error, never as clean.

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": {
      "tokenAddress": "<tokenAddress>"
    },
    "name": "token_safety_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoWhich chain the token is on. Default base.
tokenAddressYesThe token contract address: 0x... for Base, Robinhood Chain or Arc; a base58 mint for Solana or X1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world, so the description is not carrying the safety burden. It still adds real value beyond them: free, no account required, that the measurement is a simulated buy plus full sell (or the chain's measured exit), that it is a snapshot in time, and critically that an unperformable read returns an error rather than a clean result.

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 question the tool answers, then mechanism, then disclaimers and failure semantics. Every sentence carries information, though the second sentence is long and packs verdict tiers, per-chain method and cost output into one clause chain.

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 compensates by naming the verdict categories, the round-trip cost and the plain one-liner the caller receives. It also covers the failure mode (error, never a clean read) and the non-advice caveat, leaving nothing an agent needs missing before calling it.

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% and the chain enum with its default is already documented in the schema. The description restates the chain list and address formats rather than adding syntax, constraints or examples beyond it, so baseline 3 applies.

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 question it answers ("Is this token safe to buy?"), the resource (a token contract address plus chain), and the concrete output (a BASED/MID/COOKED/RADIOACTIVE verdict from a simulated round-trip). The multi-chain scope implicitly separates it from single-chain sounding siblings, but no sibling is named explicitly, so an agent must still 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?

Usage is implied by the framing question and the "measures the exit right now" line, which tells the agent this is a pre-purchase, point-in-time check. There is no explicit when-not-to-use guidance and no routing to alternatives such as robinhood_exit_check, base_verdict or token_exit_matrix.

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.