Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CORECHAIN

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

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

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?

With no annotations supplied, the description carries the full burden and does substantial work: it discloses that the call is paid, the exact price and payment chain (USDC on Base), that no account or API key is required, and that failed calls are not charged — a genuinely useful billing/error-policy disclosure. Gaps remain around rate limits, latency, and whether the returned JSON shape is stable, so it falls short of fully transparent.

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?

It is short and front-loaded, leading with 'Paid.' so the cost signal arrives before anything else, then data contents, then payment/auth terms. The sentence fragments are terse but each clause carries information; a lead-in verb would improve readability without adding bulk.

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 annotations, the description compensates by enumerating the returned fields and the payment/auth/failure terms, which is the information an agent actually needs before spending money. The one remaining gap is the concrete response format (JSON field names/structure), which is neither documented here nor in an output schema.

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 has zero properties, so there are no parameters whose meaning could be lost; the baseline for a no-parameter tool is 4. The description correctly adds no spurious parameter talk and instead describes what the parameterless call yields.

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 resource (CORECHAIN/USD live price) and enumerates the payload fields: last price, 24h open/high/low, % change, 24h and 30d volume. It also names the upstream sources (Coinbase Exchange with Kraken cross-check), which pins down the data's provenance. The verb is only implied by the telegraphic phrasing ('CORECHAIN/USD live: ...'), and it never acknowledges the hundreds of sibling buy_coin_<SYMBOL> variants, so sibling differentiation is carried by the tool name alone.

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 line ($0.002 USDC on Base) plus 'No account, no API key' gives an agent the practical precondition for deciding whether to call, which is more than nothing. However, there is no explicit statement of when to prefer this over alternatives such as buy_crypto_price or another coin variant, and no when-not guidance. Usage is inferable rather than stated.

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