Skip to main content
Glama

SouthPow crypto & market data

buy_coin_IMU

Paid. IMU/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.25 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/IMU.

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

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 reasonably well: it discloses that the call is paid ($0.25 USDC on Base), requires no account or API key, that failed calls are not charged, the underlying data sources (Coinbase Exchange with Kraken cross-check), and the endpoint. It omits rate limits, latency/freshness guarantees, and response format, which are the remaining behavioral gaps.

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?

Extremely dense and front-loaded: payment status leads, followed by returned fields, cost, auth requirements, billing policy, and endpoint. Every clause carries distinct information with no repetition or filler.

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 tool with no output schema, the description adequately enumerates the returned data fields and sources, and covers cost and failure billing. It stops short of describing the response shape (JSON structure, units, timestamp) or data freshness, which an agent might still need.

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 there is nothing to disambiguate and the baseline is high. The description reinforces this by implying the ticker is fixed in the endpoint URL, making it clear no symbol argument is needed.

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 specific resource (IMU/USD live price) and enumerates exactly which fields come back (last price, 24h open/high/low, % change, 24h and 30d volume), so an agent knows precisely what it gets. Differentiation from the hundreds of sibling buy_coin_* tools comes largely from the ticker embedded in the tool name and URL rather than an explicit statement, which keeps it just short of a 5.

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 rather than stated: an agent infers it should call this for IMU quotes and that a paid call costs $0.25. There is no explicit when-not guidance, no mention of alternatives such as buy_crypto_price or get_schema, and no note on when a cheaper/free sibling should be preferred. The payment prerequisites are covered, but selection guidance is not.

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