Skip to main content
Glama

Stoa: swaps on Robinhood Chain

List tokens

list_tokens
Read-only

Tokens Stoa lists on a network, with address, symbol and decimals, plus the router address. Any other token address can still be quoted, but treat it as unverified and run safety_check first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tokens"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoNetwork. Default robinhood.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds the non-obvious behavioral fact that the returned set is a curated/verified list rather than an exhaustive registry, and that unlisted tokens carry a trust penalty requiring safety_check. It says nothing about pagination, ordering, or caching, but those are minor for a small curated set.

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, no waste. The positive capability and the returned fields come first, followed by the caveat-and-alternative, which is the right ordering for an agent scanning for applicability.

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?

A simple single-parameter read tool with annotations covering safety and no output schema needed. The description enumerates the return fields and the verification caveat, which is sufficient to call it correctly; only the exact response shape (array vs map) is left implicit.

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 single 'chain' parameter is fully documented with its enum and default in the schema. The description's phrase 'on a network' restates rather than enriches that parameter, so it adds no syntax or semantic value 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 ('Tokens Stoa lists on a network') and even enumerates the returned fields (address, symbol, decimals, router address). It contrasts implicitly with quoting arbitrary tokens but never names a sibling tool for that path.

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 an explicit alternative condition: any token outside this list can still be quoted but should be treated as unverified and passed through safety_check first. That is real when-to-do-something-else guidance tied to a named sibling. It does not address when to use this versus stock_tokens or market_context, so it stops short of full routing coverage.

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.