Skip to main content
Glama

Stoa: swaps on Robinhood Chain

Token safety check

safety_check
Read-only

Simulate a small buy and an immediate sell-back of a token through Stoa's live router (eth_call, nothing sent), and read how concentrated its supply is. Returns verdict ok | caution | danger | unknown, buy and sell tax, round-trip cost, creator and top-10 holdings. A pass describes the token today; its owner can still change the rules.

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": "safety_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoNetwork. Default robinhood.
tokenYesToken address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds genuinely new context: the simulation runs via eth_call on the live router with nothing sent, and the result reports a bounded verdict set plus a durability caveat that the owner can change rules later. It stops short of covering failure behavior, e.g. when 'unknown' is returned or how missing liquidity is handled.

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?

Two sentences, front-loaded with the action and mechanism, followed by the return contract and one interpretive caveat. Every clause carries information an agent needs; there is no filler or repetition of the title.

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?

No output schema exists, so the description carries the return burden and discharges it by enumerating the verdict values and each reported metric. Combined with the eth_call/no-transaction disclosure and the staleness caveat, an agent has enough to call and interpret 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%, with both token and the chain enum documented in-schema, so the baseline is 3. The description adds no parameter-level meaning such as address format expectations or consequences of an unsupported chain, so it does not exceed the schema's coverage.

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?

States a concrete verb+resource pair: simulate a buy/sell round-trip through the live router and read supply concentration. It names the exact outputs (verdict, buy/sell tax, round-trip cost, creator and top-10 holdings), which makes it unmistakable against siblings like quote or build_swap that price or construct trades.

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?

The purpose implies the usage context (screen a token before trading), and the closing caveat tells the agent how to interpret a pass. But it never states when to prefer this over quote or market_context, nor any preconditions such as unsupported tokens or chains. Guidance is implied rather than explicit.

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.