Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ALLO

Paid. ALLO/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/ALLO.

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

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 at all, the description carries the full burden and does well: it discloses the paid model ($0.01 USDC on Base), the absence of account/API-key requirements, and that failed calls are not charged. Missing pieces are rate limits and latency/response shape, which matter for a paid call but are less critical given the listed 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?

Dense and front-loaded: payload, sources, price, auth posture, billing policy, URL. The leading fragment 'Paid.' is slightly cryptic and the entire body is one run-on paragraph, but almost every clause carries information an agent needs.

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?

No output schema exists, and the description compensates by enumerating the returned fields and naming the two data sources plus cross-check. A short note on failure modes or response format would make it fully self-contained, but nothing essential for a correct call is absent.

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?

Zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies a parameterless call.

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 the exact resource and scope: ALLO/USD live quote with last price, 24h open/high/low, % change, and 24h/30d volume. The ticker in the tool name plus the explicit pair in the description lets an agent pick it out from the hundreds of sibling buy_coin_* tickers 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?

Implicitly tells the agent this is the per-ticker price endpoint for ALLO, and notes payment/account requirements. But it never says when to prefer it over buy_crypto_price (a broad price tool) or other siblings, and offers no when-not guidance.

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