Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ICNT

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

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

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 notable work: it discloses that calls are paid ($0.01 USDC on Base), require no account or API key, and that failed calls are not charged. That covers the economics and auth profile an agent most needs. What it omits is the response shape and any latency or rate-limit behavior, though the listed metrics partially anticipate the payload.

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?

The text is terse and front-loaded, leading with the payment flag and the data contents before the cost and endpoint URL. The telegraphic style ('Paid.', a bare URL, unpunctuated list fragments) fits a large family of near-identical tools, though it reads as shorthand notes rather than polished prose.

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-output-schema price tool, the description supplies the essentials: what data comes back, where it is sourced, what it costs, and that no credentials are needed. Since there is no output schema, the enumerated metrics do useful double duty describing the return. A note on response format or freshness would close the remaining gap.

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 schema takes zero parameters, so the baseline is 4 and there is no parameter semantics to explain. The description correctly avoids inventing parameter talk and instead spends its words on scope and cost.

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 asset pair (ICNT/USD) and enumerates the returned metrics: last price, 24h open/high/low, % change, and 24h/30d volume. It also identifies the upstream sources (Coinbase Exchange with Kraken cross-check), which distinguishes it from the generic sibling buy_crypto_price. It stops short of an explicit verb and never states how it differs from the other per-token buy_coin_* variants, though the token symbol in the name largely handles that routing.

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 this is the tool for live ICNT pricing, and the payment terms imply a pay-per-call path. There is no explicit guidance on when to prefer this over buy_crypto_price or when a caller should look elsewhere, and no exclusions or preconditions beyond the fee note.

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