Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ROBO

Paid. ROBO/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.01 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/ROBO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that the call is paid, the exact price ($0.01 USDC on Base), the payment rail, that no credentials are required, that failed calls are not charged, and the endpoint URL. It also lists what the response contains and where the data comes from. It does not cover rate limits, caching/freshness of the quote, or response format/shape, which are the remaining gaps.

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?

It is a dense, front-loaded fragment list with no filler: cost first, then payload, then access terms, then URL. The telegraphic style ('Paid.', 'No account, no API key.') trades grammar for density, which works for an agent but reads as a spec dump rather than prose.

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 zero-parameter, no-output-schema tool, the definition covers the things an agent cannot infer: cost, payment method, credential requirements, charge-on-failure policy, and the returned fields. Missing freshness/latency expectations and any note on how errors surface, but the complexity is low enough that this is close to sufficient.

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?

The tool takes zero parameters, so the baseline is 4. The description correctly implies no input is needed beyond invoking it, and the ticker is baked into the endpoint URL, consistent with the empty 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?

The description names the exact resource (ROBO/USD) and enumerates the returned metrics: last price, 24h open/high/low, % change, 24h and 30d volume. That is enough to tell it apart from the hundreds of buy_coin_* siblings by ticker, and it names the data sources (Coinbase Exchange with Kraken cross-check). It is a noun-phrase spec rather than a verb+resource sentence, and never says 'returns price data' explicitly, which keeps it short of a 5.

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 only implied by the ticker in the name and the listed metrics; there is no statement of when to pick this over buy_crypto_price or any other sibling. The practical guidance that is present is about access rather than selection: no account, no API key, failed calls not charged. An agent can infer the use case but must do the routing itself.

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