Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ICP

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

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

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 well: it discloses the payment model and price ($0.05 USDC on Base), the settlement chain, that failures are not charged, that no authentication is needed, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It omits freshness/caching and return format, so not 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?

Everything is front-loaded — cost first, then the payload, then access terms — and there is no filler. The clipped telegraphic phrasing ('Paid.', 'ICP/USD live:') is dense but parseable; the raw endpoint URL is the only element of questionable value to an agent.

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, no-annotation, no-output-schema tool, the description covers what matters: what data comes back, where it comes from, what it costs, and that failed calls are free. Only latency/freshness expectations and the response shape are unaddressed, which is acceptable given the field list is already enumerated.

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?

There are zero input parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The symbol is baked into the tool identity and repeated in the description (ICP/USD), which is sufficient.

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 the exact resource and payload: ICP/USD last price, 24h open/high/low, % change, and 24h/30d volume. That is far more specific than the name, which reads like a trade action ('buy_coin'). It does not explicitly distinguish itself from the generic sibling buy_crypto_price, which keeps it from 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?

It implies usage context by flagging 'Paid' and the $0.05 USDC cost, so an agent can weigh cost vs. need, and it states no account or API key is required. However, it never says when to prefer this over buy_crypto_price or the other buy_coin_* variants, and gives no exclusion criteria.

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