Skip to main content
Glama

SouthPow crypto & market data

buy_coin_ILV

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description supplies valuable operational details: the $0.10 USDC charge on Base, no account or API key requirement, no charge for failed calls, and Coinbase sourcing with a Kraken cross-check. It could further clarify that the call only retrieves market data rather than purchasing ILV, and explain how payment is handled.

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?

The description is compact and front-loads the paid nature and data scope before giving cost, access, failure-billing, and endpoint details. Every fragment adds useful selection or invocation information without 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-argument fixed-asset endpoint, it covers the data provided, sources, cost, authentication requirements, failure billing, and URL. The main remaining gaps are response-format details and explicit routing guidance relative to buy_crypto_price.

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 no parameters, so the baseline score is 4. The fixed ILV endpoint URL confirms that the asset is built into the tool and that no symbol, currency, or other input must be inferred.

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 identifies a live ILV/USD market-data feed and enumerates its price, range, change, and volume metrics. This gives it clear fixed-asset scope despite the potentially misleading buy_coin name, though it does not explicitly contrast itself with buy_crypto_price.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'ILV/USD live' wording and metric list provide clear context for choosing the tool when current ILV market data is needed. It does not explain when the generic buy_crypto_price sibling would be preferable or when paying for this feed is unnecessary.

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