Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PYTH

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

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

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 does substantial work by disclosing the $0.10 USDC charge on Base, the lack of account or API-key requirements, no charge for failed calls, and Coinbase/Kraken sourcing with cross-checking. It does not explain payment execution, behavior when sources disagree, or concrete freshness and latency expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads 'Paid' and the exact data scope, then supplies cost, authentication, failure billing, and the URL without filler. Its fragment style remains easy to scan, and every clause adds operational 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 lookup with no output schema, enumerating the metrics and sources alongside cost, authentication, and failure behavior covers nearly everything needed to invoke it correctly. A short note on response format, freshness, and payment mechanics would make it more complete.

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 schema has zero parameters, so the baseline is 4 and there are no undocumented inputs requiring explanation. Fixing the asset and endpoint in the description is useful, and no further parameter semantics are needed.

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 identifies a specific resource and scope: live PYTH/USD with last price, 24-hour open/high/low, percentage change, and 24-hour/30-day volume. The metric list clarifies that this is a market-data lookup despite the purchase-like tool name, but it does not explicitly state the retrieval action or differentiate itself from buy_crypto_price.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The asset, pair, live scope, listed metrics, and exchange sources make the intended use clear: obtaining a paid PYTH market snapshot. There is no explicit when-not guidance or routing to buy_crypto_price or other buy_coin_* siblings for different assets or needs.

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