Skip to main content
Glama

SouthPow crypto & market data

buy_coin_IRYS

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

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

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 carries the full burden and does well: it discloses cost ($0.01 USDC on Base), that no account or API key is needed, that failed calls are not charged, and the upstream sources (Coinbase Exchange with Kraken cross-check). It stops short of stating rate limits, payment flow details, or response shape beyond the field list.

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?

It is compact and front-loads the most decision-relevant fact ("Paid.") before the payload and pricing details. The telegraphic fragments are efficient, though the URL is arguably redundant with the tool definition and the sentences are clipped rather than structured.

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 parameterless, annotation-free tool with no output schema, the description covers the essentials: what data returns, what it costs, what credentials are not needed, and failure billing. Only marginal items such as rate limits or freshness/latency guarantees are absent.

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 (empty object schema, 100% coverage), which is the baseline-4 case. The description correctly implies no inputs are required and adds nothing contradictory, though there is no per-parameter meaning to explain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource (IRYS/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, and 24h/30d volume. Against a sibling list of hundreds of per-ticker buy_coin_* tools, this makes the specific asset and payload unambiguous without opening any schema.

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 only implied: an agent can infer this is the tool to call for IRYS pricing data. There is no explicit when-to-use or when-not guidance, and no comparison to adjacent tools such as buy_crypto_price or buy_coin_00, so an agent must infer the routing rule from the ticker name alone.

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