Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PENGU

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

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

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 well: it discloses that the call is paid ($0.002 USDC on Base), requires no account or API key, and that failed calls are not charged. Upstream sources (Coinbase Exchange with Kraken cross-check) and the endpoint URL are also given. It stops short of explaining how payment is transacted (e.g., the payment protocol/prepay flow) or what the failure modes look like.

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?

It is dense and front-loaded — 'Paid' and the ticker/pair come first, then the payload, then the billing terms. The telegraphic fragments ('Paid.', bare URL) read clipped, and the raw endpoint URL is somewhat technical filler for an agent that just calls the tool, but no sentence is wasted.

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

Completeness5/5

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

For a zero-parameter, no-output-schema tool, the description must substitute for the missing return documentation, and it does by listing every field returned plus the vendor sources behind them. Combined with the auth ('no account, no API key') and billing ('failed calls not charged') statements, an agent has enough to call it and interpret the result correctly.

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 the baseline is 4 and there is nothing for the description to clarify. Parameter semantics are a non-issue here; the description correctly spends its words on cost and payload instead.

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 exact resource (PENGU/USD live price) and enumerates the returned fields: last price, 24h open/high/low, % change, 24h and 30d volume. That is a specific verb-and-resource statement rather than a restatement of the tool name. It doesn't explicitly contrast itself with the generic sibling buy_crypto_price, but the PENGU scope is unambiguous.

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 can infer this is the per-coin live price endpoint for PENGU versus the hundreds of other buy_coin_* siblings. There is no explicit statement of when to prefer this over buy_crypto_price or the buy_coin_* generic, and no exclusions or prerequisites named. The cost line ('$0.002 USDC on Base') gives a useful decision signal but not usage routing.

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