Skip to main content
Glama

SouthPow crypto & market data

buy_coin_OSMO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 the call is paid ($0.05 USDC on Base), requires no account or API key, is not charged on failure, and that data is sourced from Coinbase Exchange with a Kraken cross-check. It stops short of stating rate limits, latency/freshness, or whether results are cached.

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 known before anything else, then data contents, price, auth posture, and endpoint URL — every clause carries information. The telegraphic field list and raw URL at the end are slightly dense but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, yet the description enumerates the returned fields explicitly, and it covers cost, auth, failure billing, and data provenance. For a zero-parameter paid price feed, an agent has everything needed to decide and call correctly.

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 schema semantics to add and the baseline of 4 applies. The description usefully confirms the ticker is fixed in the endpoint (OSMO in the URL), so the agent knows nothing needs to be supplied.

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 (OSMO/USD) and enumerates what comes back: last price, 24h open/high/low, % change, 24h and 30d volume. That is far more specific than the ~400 sibling 'buy_coin_*' names, which only differ by ticker. The one gap is that the name says 'buy_coin' while the description describes a price-data lookup, so an agent must infer that no purchase occurs.

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?

Prerequisites and cost are stated clearly, which implies when the call is appropriate, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as the generic buy_crypto_price sibling. An agent must infer that this per-token tool is the right choice over the generic one.

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