Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ELSA

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so unusually well: it discloses that the call is paid, the exact price and payment chain ($0.01 USDC on Base), that no account or API key is needed, that failed calls are not charged (a meaningful billing guarantee for a paid tool), and the upstream data provenance (Coinbase Exchange with Kraken cross-check). An agent knows the cost, auth model, failure economics, and data reliability before calling.

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?

Two dense sentences, front-loaded with the single most decision-relevant fact ('Paid'), followed by payload contents, price, auth model, billing guarantee, and endpoint. Every clause earns its place; there is no filler or restatement of the tool name. The telegraphic style suits a tool whose caller is an agent, not a human reading docs.

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, the description compensates by enumerating the returned fields, and it covers cost, auth, failure billing, and data sources. The remaining gap is the mechanics of payment: it names the price and chain but not how the payment is attached (e.g. x402 header, pre-funded wallet) or what a payment-required failure looks like, which an agent needs to actually complete the call. Strong, but one operational step short of complete.

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 and the baseline of 4 applies. The description correctly does not waste words on an empty input object, instead spending the space on payment and data semantics.

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 a specific resource and pair (ELSA/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. It is clearly distinguishable from the hundreds of buy_coin_* siblings only implicitly, through the ticker embedded in the name and the ELSA/USD phrasing — there is no explicit 'this returns ELSA only, use buy_coin_ELA for ELA' differentiation, but the verb+resource statement is unambiguous.

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 establishes the commercial and access context ($0.01 USDC on Base, no account, no API key, failed calls not charged), which implicitly tells an agent this is callable without setup. However, it never says when to prefer this over alternatives such as buy_crypto_price (aggregated multi-coin pricing) or fetch_fact, nor does it state any preconditions like wallet balance or x402 payment handling. Usage is inferable from the ticker, not 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