Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CELO

Paid. Celo (CELO) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/CELO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden and does well on commercial behavior: $0.05 USDC on Base or Solana, no account or API key, failed calls not charged, and the exact endpoint URL. It adds no detail on rate limits, data freshness/latency, or what constitutes a failed call, which are the remaining behavioral unknowns for a paid data endpoint.

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?

Front-loaded 'Paid.' flag, then what is returned, then price/payment rails, then terms, then URL. Every clause carries distinct information and nothing is repeated.

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 paid price lookup with no output schema, the description covers cost, payment options, auth requirements, failure billing, and the fields returned. Missing only data freshness and error/response shape guidance, which are minor here.

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 makes clear the asset is fixed by the endpoint rather than passed in, which prevents an agent from hunting for a symbol argument.

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+resource implicitly ('Celo (CELO) price') and enumerates the returned fields: live USD price, 24h change, market-cap rank. It does not distinguish this 'buy_tok_' endpoint from the near-identical 'buy_coin_CELO'-style siblings or buy_crypto_price, so an agent cannot tell from the description alone which family to pick.

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 implied (call this when you need CELO spot price data) but there is no explicit when-to-use/when-not guidance, no mention of alternatives like buy_crypto_price or the buy_coin_ set, and no note on caching or repeat-call policy despite the paid nature.

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