Skip to main content
Glama

Stoa: swaps on Robinhood Chain

Market context (CoinMarketCap)

market_context
Read-only

CoinMarketCap data to put a trade in context: total crypto market cap and 24h change, BTC and ETH prices and dominance, the Fear and Greed index, and for up to 5 Robinhood Chain tokens their price, market cap, liquidity, 24h high/low, volume, trades, buyers and sellers. Use it before suggesting or explaining a trade; use quote for the price a swap actually gets.

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

Input Schema

NameRequiredDescriptionDefault
tokensNoOptional. Robinhood Chain token addresses (or symbols from list_tokens, or "native" for ETH). Leave out for the market overview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description only needs to add context. It does add the data source (CoinMarketCap) and the hard cap of 5 tokens, but says nothing about data freshness/caching, rate limits, or whether the external API can fail or return partial data — meaningful omissions for an open-world market-data call. Adequate but not rich beyond the structured fields.

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?

Two sentences with no filler: purpose and payload first, routing guidance second. The field enumeration is long but each item is substantive return information, so it earns its space, though the list density makes it slightly harder to scan than a tighter summary.

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?

With one optional parameter, no output schema, and read-only annotations, the description compensates well by enumerating the returned fields in prose. The remaining gap is operational: nothing about freshness, availability, or rate limits of the upstream market data, which matters for an open-world tool used to justify trades.

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 parameter already documents accepted formats (addresses, symbols from list_tokens, or 'native') and the omit-for-overview behavior. The description reinforces the 5-token cap and what per-token figures come back, but adds little about the parameter that the schema does not already say; baseline 3 applies.

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 specific resource (CoinMarketCap market data), enumerates exactly what it returns (total market cap and 24h change, BTC/ETH price and dominance, Fear and Greed, plus per-token price/market cap/liquidity/volume/trades/buyers/sellers), and distinguishes itself from the sibling 'quote'. An agent can tell precisely what this fetches without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use it before suggesting or explaining a trade') and names the alternative with the condition that selects it ('use quote for the price a swap actually gets'). The when-to-use and when-to-use-something-else are both spelled out rather than implied.

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.