Skip to main content
Glama

SouthPow crypto & market data

buy_coin_INJ

Paid. INJ/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/INJ.

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

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 at all, the description carries the full burden and does a reasonable job: it discloses that the call is paid, the exact price and payment chain, that no credentials are needed, that failed calls are free, and where the data comes from (Coinbase Exchange with Kraken cross-check). It does not describe latency, 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?

Front-loaded and dense — cost and data content appear in the first few words, with supporting terms after. The telegraphic style ('Paid.' as a fragment, bare URL at the end) is slightly cryptic but wastes nothing.

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 paid data lookup with no output schema, the description covers what an agent needs: the coin pair, the exact fields returned, the data sources, the price, and the auth model. Only the response shape and error behavior are left implicit.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no configuration is needed beyond the fixed URL.

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?

Names the specific resource (INJ/USD) and enumerates exactly what is returned: last price, 24h open/high/low, % change, and 24h/30d volume. That distinguishes it from the hundreds of other per-coin siblings. It does not, however, distinguish itself from the generic buy_crypto_price sibling, which is the one real ambiguity.

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?

Implied usage is clear — call this when you need live INJ/USD pricing — and the purchase terms ($0.05 USDC on Base, no account, failures not charged) tell the agent what committing to a call involves. There is no explicit 'use X instead when...' routing against buy_crypto_price or the other price sources.

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