Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CGLD

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

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

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 load and does well: it discloses cost and payment rail, that no account or API key is needed, the refund policy for failed calls, and both upstream data sources including the Kraken cross-check. It stops short of rate limits, HTTP method, or response shape, which keeps it from a 5.

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 — cost and data payload lead, provenance and URL trail. The telegraphic fragments ('Paid.', 'No account, no API key.') read efficiently but are clipped enough that prose clarity is slightly reduced.

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 no output schema and no parameters, the description compensates by enumerating the returned metrics and naming the price sources, so an agent knows what comes back. The absence of response encoding details and rate limits is the only remaining gap for a paid data endpoint.

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 adds no parameter detail because the asset is baked into the endpoint. Nothing is left ambiguous about inputs.

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 verb+resource (CGLD/USD live price) and enumerates exactly which data points are returned: last price, 24h open/high/low, % change, 24h and 30d volume. Among hundreds of near-identical buy_coin_* siblings, the asset symbol and payload contents make it unambiguous.

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?

It signals that the call is paid ($0.10 USDC on Base) and that failed calls are free, which is meaningful guidance about when it is safe to invoke. However, it never says when to prefer it over the generic sibling buy_crypto_price or how it relates to other buy_coin_* endpoints, leaving the alternative-selection question 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.

Resources