Skip to main content
Glama

SouthPow crypto & market data

buy_coin_FLR

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 it does disclose important behavior: the call is paid, costs $0.002 USDC on Base, requires no auth, and failures are not charged, plus the data provenance (Coinbase Exchange with Kraken cross-check). It omits the HTTP method, what a paid-but-empty or stale response looks like, latency, and whether the URL is the complete endpoint. Solid but not full on a financial mutation-of-wallet tool.

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 cost, then the payload contents, then access terms, then the endpoint. Dense but every clause carries information. The telegraphic fragments ('Paid.', bare URL at the end) are slightly rough but not wasteful.

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-input read tool with no output schema and no annotations, the description covers what data comes back, what it costs, what auth is needed, and where it is called. The main remaining gap is error/response format, which matters somewhat given the paid model but is minor at this complexity.

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 input schema has zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly adds no parameter noise and instead spends its words on cost and return fields.

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?

States a specific resource (FLR/USD live price) and enumerates exactly what is returned: last price, 24h open/high/low, % change, 24h and 30d volume. An agent knows precisely what it gets. Differentiation from the hundreds of siblings is carried by the coin suffix in the name rather than the description, so it stops short of 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?

Conveys practical preconditions for calling it (paid, no account, no API key, failed calls not charged), which is real usage guidance. However, it never states when to prefer this over a free alternative such as buy_crypto_price, and gives no guidance on caching or repeated calls given the per-call cost.

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