Skip to main content
Glama

SouthPow crypto & market data

buy_tok_IQ

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

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

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 substantial work: it discloses that the call is paid, the exact price ($0.01 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. That refund-on-failure note is exactly the kind of behavior an agent needs before spending. It stops short of describing the response format or how the payment handshake works, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short clauses, front-loaded with the 'Paid' flag and the data fields, then the cost, then the access preconditions, then the URL. No filler and no repetition; each sentence adds a distinct decision-relevant fact.

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-param paid endpoint with no output schema, the definition covers what is returned, the price, the payment rails, the auth model, the failure-charging policy, and the raw URL. The main gaps are the absence of any routing hint versus buy_coin_IQ and no indication of response encoding, both minor for a tool this simple.

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 compensate for. The schema being empty is consistent with the description, which describes a fixed-endpoint lookup.

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 a concrete resource and result set: live USD price, 24h change and market-cap rank for IQ. An agent knows exactly what data it gets. It loses a point because it never distinguishes itself from the near-identical sibling buy_coin_IQ or from buy_crypto_price, so selection between those three rests on the name alone.

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 by the resource ('price of IQ'). The 'Paid... $0.01 USDC on Base or Solana. No account, no API key' lines give the agent the cost and access preconditions it needs to decide whether to spend, which is real guidance. However there is no explicit statement of when to prefer this over buy_coin_IQ or the generic buy_crypto_price, and 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