Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FIGHT

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

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

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 exact cost ($0.002 USDC on Base), that no account or API key is required, that failed calls are not charged, and that data is sourced from Coinbase Exchange with a Kraken cross-check. Remaining gaps are rate limits and response latency.

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?

Roughly five short fragments, all front-loaded with the payment requirement before the data payload and pricing. Every element earns its place, though the telegraphic style ('Paid.', bare URL) is slightly terse for an agent parsing it cold.

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, annotation-free tool, the description supplies the essentials an agent needs: cost, payment rail, auth posture, failure billing policy, and the data fields. Only rate limits and explicit return shape remain unaddressed.

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 the baseline is 4; there is no parameter meaning for the description to add or omit.

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 states a specific verb+resource: live FIGHT/USD price data, enumerating the exact fields returned (last price, 24h open/high/low, % change, 24h and 30d volume). It is clearly distinguishable from siblings only via the ticker in the name, not through any explicit differentiation in the text, so it falls short of 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?

The leading 'Paid.' and the pricing line imply this is the metered path to FIGHT pricing data, which gives implicit usage context. However, it never states when to prefer this over the generic buy_crypto_price sibling, nor any when-not conditions, leaving routing to inference.

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