Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CAP

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

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

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?

No annotations are supplied, so the description carries the full behavioral burden, and it does cover the operationally important traits: paid call, price and payment chain, no authentication required, and no charge on failure. What is missing is the response format and any rate/latency limits, which matter for a paid endpoint. This is above-average disclosure for an unannotated tool but not exhaustive.

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 first token is 'Paid.', which front-loads the single most decision-relevant fact, followed by data contents, price, auth, and failure policy in a compact sequence. The bare URL at the end is slightly awkward as prose but useful as the endpoint reference. Nothing here is filler, though the fragment style is terse to the point of being note-like.

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 does real work: it lists the returned fields, names the data sources, and spells out payment and failure behavior. The remaining gap is the exact response shape (JSON keys, timestamp format), which an agent would have to discover by calling. That is a minor omission rather than a blocking one given how simple the tool is.

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 input schema is an empty object with zero properties, so there are no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no parameter prose, instead spending its words on output content and payment terms.

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 enumerates exactly what is returned for the CAP/USD pair: last price, 24h open/high/low, percent change, and 24h/30d volume, plus the exchanges used as sources. That is specific enough to distinguish it from any other buy_coin_<TICKER> sibling, since the asset and data set are both named. It never states the action verb clearly ('Paid.' then a field list), and given the 'buy_coin_' name an agent might briefly wonder whether this purchases the coin rather than fetches its price.

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?

The cost notice ('$0.25 USDC on Base', 'No account, no API key', 'Failed calls not charged') tells the agent this is a payable call and what the spend will be, which is meaningful when choosing whether to invoke it. However, there is no explicit statement of when to prefer this over siblings such as buy_crypto_price or another ticker variant, and no exclusion for stale/duplicate lookups. Usage is implied by the ticker in the name rather than guided.

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