Skip to main content
Glama

SouthPow crypto & market data

buy_coin_LA

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

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

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 that the call is paid ($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. Missing are rate limits, latency expectations, and result freshness/caching behavior, which keeps it below 5.

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.' so cost is known before anything else, then the payload contents, then payment terms, then the endpoint URL. Dense and nearly waste-free; the telegraphic fragments ('Paid.', 'No account, no API key.') trade a little readability for compactness.

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 tool with no output schema, the description supplies the return fields, cost, payment chain, auth posture, and failure billing policy. What is absent is the actual response shape and units/formatting, which matters more than usual because there is no output schema to fall back on.

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 properties, so there is nothing for the description to disambiguate; the baseline of 4 applies. It correctly avoids fabricating parameters and instead spends its words on what the call returns.

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 names the specific asset pair (LA/USD) and enumerates exactly what comes back: last price, 24h open/high/low, % change, 24h and 30d volume, plus the source venues. That distinguishes it cleanly from the hundreds of sibling buy_coin_* tools. It stops short of a stated verb (e.g. 'fetches'), relying on the parameterless 'live:' framing, so a 4 rather than 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?

Usage is only implied: an agent infers it should call this when it needs LA price data rather than, say, buy_crypto_price or a generic market tool. No explicit when-to-use or when-not guidance and no mention of the generic sibling it might be confused with. The cost/auth disclosure indirectly supports a spend decision but is not routing guidance.

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