Skip to main content
Glama

SouthPow crypto & market data

buy_tok_IOTA

Paid. IOTA (IOTA) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/IOTA.

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

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 carries the full behavioral burden and does substantial work: it discloses the price ($0.01 USDC), the accepted payment chains (Base or Solana), the absence of authentication requirements, and a billing policy for errors ('Failed calls not charged'). That last detail is genuinely useful for an agent deciding whether to retry. It stops short of stating rate limits, freshness/latency, or response format.

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?

Extremely compact and front-loaded: cost first, then payload, then payment rails, then billing policy. Every clause carries information. The trailing endpoint URL is of marginal value to an agent that invokes the tool rather than calling HTTP directly, but it is not harmful.

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 data tool, the description supplies what an agent actually needs: the returned fields, the cost, the payment networks, and the no-auth property. The main remaining gap is that it never explains how this endpoint relates to the nearly identical buy_coin_<SYMBOL> tools, which is the primary ambiguity in this catalog.

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 the baseline is 4; there is nothing for the description to disambiguate. The description correctly implies no arguments are needed by naming the asset inline in the tool itself.

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 specific asset (IOTA) and enumerates the exact payload: live USD price, 24h change and market-cap rank. That is a concrete resource-plus-fields statement rather than a restatement of the name. It does not distinguish itself from the large buy_coin_* family or buy_crypto_price, so an agent cannot tell from the text alone whether this differs from those siblings.

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: the 'Paid. ... $0.01 USDC on Base or Solana. No account, no API key' framing tells the agent this is a pay-per-call endpoint usable without setup, which is a real precondition. However, there is no explicit statement of when to choose this over buy_coin_* or buy_crypto_price, and no exclusions or alternatives are named.

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