Skip to main content
Glama

SouthPow crypto & market data

buy_tok_IUSD

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

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

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 supplied, the description carries the full behavioral burden and does well: it declares the paid/cost model, the accepted payment rails, the absence of authentication, and the failure-charging policy, plus the endpoint URL. It stops short of describing response shape beyond the three named fields, latency, caching, or rate limits.

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 five short clauses, front-loaded with what the tool returns, then cost, then access requirements, then the URL. Nothing is padded and no sentence 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 no-parameter, single-asset price lookup with no output schema and no annotations, this covers the essentials an agent needs to decide and call: what data comes back, what it costs, how to pay, and that failures are free. Only return-format and freshness details are missing, which is minor at this complexity.

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 input schema has zero parameters, so there is no parameter semantics to explain and the baseline is 4. The description correctly signals that the asset is baked into the tool rather than passed as an argument, which prevents an agent from looking for a symbol parameter.

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 (InfiniFi USD / IUSD) and the exact payload it returns: live USD price, 24h change, and market-cap rank. That is enough for an agent to tell it apart from the many sibling price tools, although the differentiation comes entirely from the asset symbol rather than any explicit contrast with siblings such as 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 Guidelines3/5

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

The description gives strong preconditions for calling it: $0.05 USDC on Base or Solana, no account, no API key, and no charge on failure. What it does not do is say when to prefer this over an overlapping alternative (for example a general crypto-price tool) or when the call would be redundant, so the when-to-use guidance is implied rather than stated.

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