Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BOBBOB

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

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

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, the description carries the full burden and does well: it discloses that calls are paid ($0.05 USDC on Base), that no auth is needed, that failures are not billed, and that data is sourced from Coinbase Exchange with a Kraken cross-check. It stops short of explaining the payment handshake (how the $0.05 is settled for a zero-parameter tool) or the response shape.

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?

Telegraphic and front-loaded: the paid status and data payload lead, then cost, then auth and billing guarantees. Nearly every clause earns its place; the trailing raw URL is the one element of marginal value to an agent that cannot call it directly.

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 return payload, and it does so field by field. Payment, auth, and failure billing are all covered; the remaining gap is how the payment is actually transacted on a parameterless tool, which an agent would need to know before invoking.

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 and there is nothing for the description to disambiguate. The quoted 'BOBBOB/USD' does usefully pin down the implicit argument (the asset pair) that the empty schema cannot express.

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 (BOBBOB/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. The verb is implicit rather than stated ('Paid.' followed by a data list), and the differentiation from siblings is carried by the tool name and the quoted pair rather than an explicit sentence.

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?

It gives important usage preconditions — the $0.05 USDC-on-Base cost, no account or API key required, and no charge for failed calls — which is real decision-relevant context. It does not say when to pick this over the generic sibling buy_crypto_price or any other quote source, so the call/no-call decision is only partially supported.

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