Skip to main content
Glama

SouthPow crypto & market data

buy_coin_SHPING

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does so well: it discloses the price ($0.002 USDC), settlement rail (Base), that no account or API key is needed, that failed calls aren't charged, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It stops short of describing latency, caching, or the response envelope, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Telegram-terse but front-loaded: payment status first, then payload contents, then cost/auth/failure terms, then the endpoint. Every clause carries operational information an agent needs before spending money; nothing is padding.

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?

There is no output schema, so the description must convey the return payload, and it does by enumerating fields and naming the data sources. Missing only details like response shape or staleness/latency, which matter for a priced market-data call but are minor against what is supplied.

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 to disambiguate; the baseline applies. The description correctly implies the ticker is fixed by the tool itself rather than passed as an argument, avoiding any false expectation of a symbol parameter.

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 resource (SHPING/USD live price) and enumerates exactly what data is returned: last price, 24h open/high/low, % change, 24h and 30d volume. Combined with the ticker-scoped name, an agent can distinguish it from the hundreds of sibling buy_coin_<TICKER> tools without opening a schema.

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 description makes the paid nature and cost clear ('$0.002 USDC on Base', 'Failed calls not charged'), which implicitly informs a cost/benefit decision, but it never names an alternative such as the generic buy_crypto_price sibling or states when to prefer one over the other. Usage is implied by the ticker 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