Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PYR

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

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

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, the exact price ($0.05 USDC on Base), that no auth is required, that failed calls are free, and the upstream sources used. It stops short of explaining how payment is settled or what the response payload looks like.

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?

Roughly forty words that front-load the most decision-relevant fact — that the call costs money — then the returned fields, the price, the auth requirement, the failure policy, and the endpoint. Every clause carries information; nothing is redundant.

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, no-output-schema tool, the description substitutes for the missing return schema by enumerating exactly which metrics come back and from which exchanges. Payment mechanics and response encoding are left unstated, but those are likely protocol-level concerns rather than per-tool ones.

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 to disambiguate; the schema is empty and fully described. Baseline 4 applies, and nothing in the description contradicts or muddies the no-argument contract.

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?

States a specific resource — live PYR/USD price with a named field list (last, 24h OHLC, % change, 24h/30d volume) and named sources (Coinbase Exchange, Kraken cross-check). The symbol is embedded in the tool name and description, so it is distinguishable from the other buy_coin_* siblings. It does not, however, mention the generic buy_crypto_price sibling or explain the relationship to it.

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 listed (this is the tool for live PYR/USD quotes), and useful access conditions are stated (no account, no API key, failed calls not charged). It never says when to prefer this over buy_crypto_price or another quote source, and gives no exclusions.

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