Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ESP

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.002 USDC on Base), that no account or API key is needed, that failed calls are not charged, and the upstream data sources. It omits rate limits and response shape, but 'failed calls not charged' is a genuinely useful risk disclosure for a metered call.

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 front-loaded, starting with 'Paid.' and then the data payload, then cost and auth terms. The telegraphic style ('% change', '24h and 30d volume') is dense but readable; the raw URL at the end is arguably the least valuable element but serves as an endpoint reference.

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, no-output-schema data tool, the description covers the essentials: what data comes back, where it comes from, what it costs, and that failures are free. Missing only response-format and rate-limit details, which are minor given the low complexity.

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 instead spends its words on what the parameterless call yields and costs, which is the right use of space.

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 and metric set: ESP/USD last price, 24h open/high/low, % change, and 24h/30d volume, with named data sources (Coinbase Exchange, Kraken cross-check). An agent can tell exactly what data this returns and, via the ticker suffix, that it is the ESP-specific variant of the buy_coin_* family. It stops short of explicitly distinguishing itself from generic siblings like buy_crypto_price.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no pointer to alternatives such as buy_crypto_price or other buy_coin_* entries. The cost and access notes ('$0.002 USDC on Base. No account, no API key.') implicitly frame a paid-call decision, but the agent must infer selection rules itself.

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