Skip to main content
Glama

SouthPow crypto & market data

buy_coin_PNUT

Paid. PNUT/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.01 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/PNUT.

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

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 at all, the description carries the full burden and does well: it discloses the pay-per-call model, the exact price and payment chain, that no credentials are needed, that failed calls are not billed, and the upstream data sources (Coinbase Exchange with Kraken cross-check). What's missing is rate limits, latency, and the response format, but the core economic and access behavior is disclosed clearly.

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.' then the data payload, then price, then access terms — a sensible ordering. It is telegraphic and jargon-dense but every fragment carries information; nothing is padding.

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?

With no output schema and no annotations, the description substitutes by listing the exact returned fields, which is the key missing piece. Remaining gaps are response encoding and numeric precision/units, but an agent can call this correctly with what's given.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly doesn't waste space restating an empty schema.

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 a specific resource (PNUT/USD live price) and enumerates exactly what comes back: last price, 24h open/high/low, % change, 24h and 30d volume. Sibling differentiation is implicit through the token symbol in the name and the explicit endpoint URL, though it never says outright 'this is the PNUT feed, not other tokens'. Note the tool name says 'buy_coin' while the description describes a read-only price feed, which slightly muddies the verb.

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 'call this when you need PNUT price data'. Cost and access conditions ($0.01 USDC on Base, no account, no API key, failed calls free) give practical context for deciding whether to call. However, no alternatives are named — nothing points to buy_crypto_price or explains when a different sibling is the right choice.

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