Skip to main content
Glama

SouthPow crypto & market data

buy_tok_POWER

Paid. Power Protocol (POWER) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/POWER.

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

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 carries the full burden and does substantial work: it discloses the paid nature, the exact cost ($0.01 USDC), the two supported payment rails (Base or Solana), that no account or API key is needed, and that failed calls are not charged. That billing-on-failure policy is exactly the kind of operational detail an agent cannot get from structured fields. It stops short of rate limits, latency, or response shape, keeping it out of the top band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly thirty words with zero redundancy, front-loaded with the cost flag before the data description, then terms, then billing policy, then the raw endpoint URL. Each clause delivers a distinct fact and none restate the tool name.

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 parameterless, single-symbol price lookup with no output schema, the description covers what an agent needs to decide and pay: what data comes back, the price, the rails, the auth posture, and the failure-charge rule. The only gap is the exact response structure, which is acceptable here because no output schema exists and the returned fields are already enumerated.

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, which is the baseline-4 case, and the schema is empty at 100% coverage, so there is nothing for the description to compensate for. The description correctly implies the ticker is fixed (POWER) rather than passable as an argument, which prevents an agent from hunting for a symbol parameter.

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 resource precisely (Power Protocol / POWER) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. It is clearly a market-data lookup rather than a trade or audit, which separates it from the buy_audit_* and buy_domain_* siblings. It loses a point only because differentiation from same-shaped siblings (buy_coin_*, buy_crypto_price) rests entirely on the embedded ticker rather than on any stated distinction.

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 — an agent can infer this is the endpoint for POWER pricing — but there is no explicit when-to-use framing, no statement of when NOT to use it, and no pointer to overlapping alternatives such as buy_crypto_price or the buy_coin_ family. The 'Paid' prefix at least signals this is not a free call, but no routing guidance accompanies it.

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