Skip to main content
Glama

SouthPow crypto & market data

buy_coin_IMX

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

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

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 supplied, the description carries the full burden and does well: it discloses the payment model and exact price ($0.002 USDC on Base), that no account or API key is required, and that failed calls are not charged — all behavioral facts an agent cannot get from the empty schema. It loses a point for not stating data freshness/delay, rate limits, or what a failure response looks like.

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?

A single dense paragraph with the commercial terms front-loaded ('Paid.') followed by payload, sources, cost, access requirements, and the endpoint URL — good front-loading and no filler sentences. The terminal raw URL is slightly out of place for an agent that only needs to call the tool, but it is short and plausibly useful for verification.

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 annotations and no output schema, the description covers the essentials: what data is returned, where it comes from, what it costs, and that failures are free. The main residual gap is that with no output schema the return format (JSON shape, units, timestamp field) is implied by prose rather than specified.

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, which is the baseline-4 case; there is no parameter meaning to add and the description correctly does not invent any. The coin and quote currency are baked into the tool itself (IMX/USD), so the absence of arguments is coherent rather than an omission.

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 gives a specific verb+resource: it returns IMX/USD live market data, and it enumerates exactly which fields come back (last price, 24h open/high/low, % change, 24h and 30d volume) plus the sources (Coinbase Exchange with Kraken cross-check). That is far beyond restating the name. It stops short of 5 because it never explicitly contrasts itself with the ~250 sibling per-coin tools or with buy_crypto_price, leaving the differentiation to the tool 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 implied rather than stated: an agent can infer 'call this when you need a live IMX price,' and the '$0.002 USDC on Base / no account, no API key' line supplies real prerequisites for deciding to invoke it. However, there is no explicit when-to-use guidance, no mention of when another tool (buy_crypto_price or a sibling coin tool) would be preferred, and no note on freshness or rate limits that would affect invocation timing.

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