Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FLOKI

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

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

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 does substantial work: it discloses the $0.10 USDC-on-Base price, that no account or API key is required, that failed calls are not charged, the upstream data sources (Coinbase Exchange with Kraken cross-check), and the endpoint URL. It stops short of latency, rate limits, or how payment is actually settled, which are the remaining unknowns before invoking a paid call.

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 with 'Paid.' and the field list, and every fragment carries information — price, sources, cost, auth model, failure policy, URL. The telegraphic style is efficient but slightly staccato, with no explicit statement of what the response looks like as a whole.

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?

With no output schema, the description compensates by enumerating the returned fields and the data sources, and it covers prerequisites (none), cost, and failure behavior — everything needed to decide and pay. Only the response format (e.g., JSON structure) and payment mechanics 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 nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies the ticker is fixed by the tool itself rather than supplied as input.

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 exact resource (FLOKI/USD live price) and enumerates the returned fields (last, 24h OHLC, % change, 24h/30d volume), so an agent knows precisely what it gets. It does not explicitly contrast itself with the generic sibling buy_crypto_price or say 'this is the FLOKI-only variant', leaving sibling differentiation to the ticker in the name.

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 by the content (use this when you need live FLOKI/USD quote data), and it usefully states the access model (no account, no API key) and cost. There is no explicit when-not-to-use guidance and no pointer to alternative quote tools such as buy_crypto_price for multi-asset needs.

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