Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BLUR

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does unusually well: it discloses that the call is paid ($0.01 USDC on Base), that no account or API key is required, that failed calls are not charged, and that figures are cross-checked against Kraken. It omits latency, rate limits, and any notion of staleness/caching, 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 the valuable part ('Paid' plus the data fields) before pricing, auth, and URL details, and every clause carries information. The style is telegraphic and the trailing raw URL is of marginal value to an agent that already has the endpoint, but nothing is padded.

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 must describe the payload, and it does: it enumerates the returned metrics and their provenance. Given a zero-parameter, single-endpoint tool this is close to sufficient; the only real gap is response shape/format (JSON structure, units, timestamps) which an agent must discover by calling.

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 no parameter semantics to document; baseline is 4. The description instead spends its words on what the parameterless call returns, 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource and scope: live BLUR/USD pricing with an enumerated field list (last, 24h OHLC, % change, 24h/30d volume) and named upstream sources (Coinbase Exchange, Kraken cross-check). The ticker-specific name plus this field list makes it trivially distinguishable from the hundreds of sibling buy_coin_* tools.

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 the ticker rather than stated: an agent can infer 'call this for BLUR spot data,' but the description never names alternatives such as buy_crypto_price for a general lookup or a sibling coin tool for a different asset, nor does it say when this is the wrong choice. The cost and 'failed calls not charged' lines do help the agent decide whether to invoke at all, which lifts it above a bare 2.

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