Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ORCA

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

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

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 does real work: it discloses the paid model ($0.01 USDC on Base), the lack of account or API key requirements, the failure policy ('failed calls not charged'), the upstream data sources (Coinbase Exchange with Kraken cross-check), and the endpoint URL. The notable gap is that it never explains how payment is settled for a zero-parameter tool, so an agent cannot anticipate whether a wallet or pre-funded balance is needed.

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?

The definition is short, front-loaded with the cost signal, and every clause carries distinct information (data fields, sources, price, auth model, failure policy, URL). The telegraphic fragment style ('Paid.' / 'No account, no API key.') is dense but slightly reduces readability compared with full sentences.

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?

Because there is no output schema, the description must convey return contents, and it does by listing the exact metrics included. For a zero-parameter price feed that is nearly sufficient; the remaining omission is the response shape (field names, units/quote currency of volume, refresh cadence) and any latency expectation an agent should assume before retrying.

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 no parameters, so there is nothing for the description to disambiguate beyond the fixed pair. Baseline 4 applies. The description correctly signals that the ticker is baked into the endpoint rather than passed as an argument, which prevents an agent from trying to supply a symbol.

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 and pair (ORCA/USD) and enumerates the specific metrics returned: last price, 24h open/high/low, % change, 24h and 30d volume. That is far more specific than the sibling names alone, which only differ by ticker. It falls short of a 5 because the leading 'Paid.' and the 'buy_coin_' name prefix imply a purchase action while the body describes a read-only price feed, leaving a small ambiguity about what the call actually does.

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 subject matter: call this when you need live ORCA pricing. There is no explicit statement of when to prefer this over the generic buy_crypto_price sibling or over any other buy_coin_* tool, and no exclusions such as staleness limits or which venues are authoritative. The agent must infer routing from the ticker in the name.

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