Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BIO

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

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

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?

With no annotations, the description carries the full burden and does well: it discloses the x402-style payment ($0.05 USDC on Base), that no account or API key is required, that failed calls are not charged, and the data provenance. It stops short of stating latency, update cadence beyond 'live', or the response envelope, which keeps it out of 5 territory.

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 payment flag and the payload contents, then cost, then access requirements, then URL — a sensible priority order with no filler. The telegraphic style ('Paid.', 'No account, no API key.') reads as clipped but every clause carries information.

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 paid quote endpoint with no output schema, the description enumerates the returned fields and discloses cost and auth model, which is enough for correct invocation. The remaining gap is the response shape/units (e.g., whether % change is decimal or percent, which timestamp defines '24h'), which matters for a pricing tool.

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 is 4. The description correctly implies the asset is fixed by the endpoint (BIO embedded in the URL), so an agent knows no symbol argument is needed.

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?

Names a specific resource and scope: live BIO/USD with last price, 24h open/high/low, % change, and 24h/30d volume, plus the upstream venues (Coinbase Exchange with Kraken cross-check). This makes it trivially distinguishable from the ~400 sibling buy_coin_* tools, each of which is the same endpoint for a different asset.

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 data content and the 'Paid' + $0.05 price tag, so an agent can infer this is the quote tool for BIO specifically. However, it never states when to prefer this over the generic buy_crypto_price or how to handle multi-asset queries, and it gives no guidance on retry behavior despite mentioning failed calls are free.

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