Skip to main content
Glama

SouthPow crypto & market data

buy_coin_UP

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

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

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 at all, the description carries the full burden and does well: it discloses that the call is paid ($0.25 USDC on Base), requires no account or API key, that failed calls are not charged, and names the upstream data sources (Coinbase Exchange with Kraken cross-check). It does not cover rate limits, response format, or latency, which keeps it short of 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.

Conciseness4/5

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

Front-loaded with 'Paid.' so cost is the first thing an agent sees, followed by field list, pricing/auth, and endpoint URL. It is telegraphic but each clause carries distinct information; the only minor cost is the staccato phrasing that reads as a list rather than prose.

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-annotation data-fetch tool, the description covers cost, auth, failure billing, data provenance, and the returned fields — enough to call it safely. Missing only the response format and freshness/caching semantics, which no output schema supplies.

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 the baseline is 4. The description confirms this implicitly by embedding the asset and endpoint in the URL rather than exposing configurable options, leaving nothing for an agent to mis-supply.

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 (UP/USD live market data) and enumerates the specific fields returned: last price, 24h open/high/low, percent change, 24h and 30d volume. It is clearly distinguishable from sibling buy_coin_* tools by the asset symbol. It lacks an explicit verb ('returns'/'fetches'), relying on the field list to imply retrieval.

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 only implied: an agent infers it should call this when it needs UP/USD spot data. There is no explicit when-to-use statement, no exclusions, and no pointer to alternatives such as buy_crypto_price or buy_coin_00 for related price lookups, even though hundreds of similar siblings exist.

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