Skip to main content
Glama

SouthPow crypto & market data

buy_coin_XCN

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

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

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 behavioral load and does well: it discloses that the call is paid ($0.002 USDC on Base), that no account or API key is needed, that failed calls are not charged, and which exchanges the data comes from. It omits rate limits, latency, and expected response shape, which are the remaining gaps for a zero-annotation tool.

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, then payload, then payment/auth terms, then endpoint URL. Every fragment carries information, though the telegraphic style ('Paid.', 'No account, no API key.') is terse enough that the endpoint URL feels like the only element that could be moved to the schema.

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 parameterless, output-schema-less, annotation-free tool, this covers the essentials an agent needs: what data comes back, what it costs, how payment is settled, and that failures are free. What is missing is the concrete return structure and any indication of freshness or caching, which matters for a 'live' price claim.

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 and the schema is empty, so there is nothing for the description to disambiguate; baseline applies. The description usefully spends its words on scope and cost instead of restating a schema that has no fields.

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 specific resource (XCN/USD live price) and enumerates exactly what it returns: last price, 24h open/high/low, % change, 24h and 30d volume, with named data sources. An agent can tell this apart from siblings only by the asset ticker, though, and the 'buy_coin_' name prefix suggests a purchase action while the text describes a paid data feed, which is never reconciled.

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 by 'XCN/USD live' – it fetches live pricing for one asset – but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as the generic buy_crypto_price tool or the other buy_coin_<TICKER> variants. The 'No account, no API key' line is a prerequisite, not routing guidance.

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