Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PLU

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the behavioral burden, and it does disclose the important traits: monetization model and price, absence of authentication, the failure-charging policy, and even the underlying data sources (Coinbase Exchange with Kraken cross-check). Remaining gaps include how payment is actually settled (wallet/flow), latency or data freshness, and any rate limits.

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?

Extremely compact, with the cost warning front-loaded and no filler sentences. The telegraphic fragment style ('Paid.', 'No account, no API key.') is dense but slightly cryptic, and the raw endpoint URL at the end adds little for an agent that invokes the tool rather than fetches the URL manually.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe return values, and it does enumerate the fields returned. However, it omits the response shape (JSON envelope, units, null handling) and, more importantly, does not explain the mechanics of the $0.10 USDC payment on Base, which is the single most consequential unknown for an agent deciding whether it can call this at all.

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 adds no parameter discussion, instead spending its words on scope and cost.

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 exactly what the tool returns for a specific asset: 'PLU/USD live: last price, 24h open/high/low, % change, 24h and 30d volume'. Token specificity is inherent in the name, so it is separable from the hundreds of buy_coin_* siblings. It never uses an explicit verb like 'get' and opens with 'Paid.', which delays the purpose statement slightly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear context is supplied: the call is paid, costs $0.10 USDC on Base, requires no account or API key, and failed calls are not charged. This tells an agent both the prerequisite profile and the downside risk of invoking it. What is missing is routing guidance against near-alternatives such as buy_crypto_price or a different ticker's variant, and there is no explicit when-not-to-use statement.

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