Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SPELL

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

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_SPELL"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/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 well: it discloses the cost ($0.10 USDC on Base), the payment rail, that no account or API key is required, the failure policy (failed calls not charged), the upstream data sources, and the endpoint URL. It omits rate limits, latency/freshness guarantees, and response format, which keeps it out of the top band.

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?

The description is compact, front-loaded with 'Paid.' and the data payload, followed by pricing, access, and billing terms. The telegraphic style crams a lot into few words, though the fragmented phrasing ('Paid.', bare field list) is a bit terse for easy scanning.

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 tool with no output schema, the description supplies enough to call it correctly and anticipate cost and results, since it enumerates the returned fields. Missing details are secondary: response serialization format, data freshness, and rate limits.

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 and there is nothing for the description to disambiguate. The included endpoint URL is incidental rather than a parameter explanation, but no parameter gap exists.

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?

The description names the exact resource (SPELL/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume, plus the sources (Coinbase Exchange with Kraken cross-check). Combined with the ticker-encoded tool name, an agent can distinguish it from the hundreds of sibling ticker tools 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 Guidelines3/5

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

Usage is only implied: the tool is clearly the SPELL-specific price feed, so the when-to-use case is inferable from the ticker. There is no explicit guidance on when to prefer this over buy_crypto_price or buy_coin_00, and no stated exclusions or prerequisites beyond the price point.

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