Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CT

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description does real work by disclosing the payment model ($0.05 USDC on Base), the absence of auth requirements, and the fact that failed calls are not charged — exactly the risk information an agent needs before spending. It stops short of rate limits, latency, or what a failure response looks like, which matters for a paid endpoint.

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?

Front-loading 'Paid.' is good practice for a metered call, and the payload/data-source/cost/auth facts are packed into a few short clauses with no filler. The telegraphic style and trailing raw URL are slightly rough but nothing is wasted.

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, fixed-endpoint price lookup with no output schema, the description covers what is returned, where the data comes from, and what the call costs and requires. Only failure modes and rate-limit behavior are left unspecified.

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 there is nothing for the description to disambiguate; the baseline applies. All variability (which asset, which data points) is fixed in the tool identity and description rather than in arguments.

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 names the exact pair (CT/USD) and enumerates the returned metrics: last price, 24h open/high/low, % change, 24h and 30d volume, plus data sources (Coinbase Exchange, Kraken cross-check). The verb is implicit rather than stated, but an agent can immediately tell this is a spot price lookup for the CT token rather than, say, a news or insider feed.

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 gives decision-relevant context (cost, no account or API key, no charge on failure) but never states when to prefer this over alternatives such as buy_crypto_price or another buy_coin_* ticker. The ticker scoping is carried by the tool name alone, so sibling selection is implied rather than explained.

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