Skip to main content
Glama

SouthPow crypto & market data

buy_tok_IOTX

Paid. IoTeX (IOTX) 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/IOTX.

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

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 burden and does reasonably well: it discloses that calls are paid ($0.01 USDC on Base or Solana), that failed calls are not charged, and that no account or API key is required — all facts an agent cannot get from the empty schema. It omits response format details and any rate limits, keeping it short of a 5.

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?

Terse fragments, but front-loaded with the most decision-relevant token ('Paid.') followed by what is returned, then price and access terms, then endpoint. Every clause carries information; the telegraphic style is efficient rather than sloppy.

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 price lookup with no output schema, the description supplies the returned fields, the cost, the payment rails, and the endpoint — enough to invoke confidently. The one missing piece is any differentiation from buy_coin_IOTX, which covers the same asset under a different naming family.

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 there is nothing for the description to disambiguate; baseline applies. The description correctly implies no inputs are needed beyond invocation and payment.

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 verb and resource (buy IoTeX/IOTX price) and enumerates the returned fields: live USD price, 24h change, market-cap rank. It does not, however, explain how it differs from the near-namesake sibling buy_coin_IOTX or from buy_crypto_price, which an agent seeing both would want resolved.

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 context is implied by price-data content and the 'Paid' prefix, and the description gives practical gating facts (no account, no API key, $0.01 USDC on Base or Solana). But it never says when to pick this over the equivalent buy_coin_IOTX or the generic buy_crypto_price tool, so the agent is left to infer the routing.

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