Skip to main content
Glama

SouthPow crypto & market data

buy_tok_POD

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the call is paid ($0.05 USDC), payable on Base or Solana, requires no account or API key, and that failed calls are not charged. It omits how payment is actually authorized (e.g., x402 flow) and any rate/retry limits, 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?

It is compact and front-loaded, leading with 'Paid.' so cost is known before anything else. The endpoint URL is somewhat redundant with the tool name but is genuinely useful metadata; otherwise every clause earns its place.

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 simple zero-parameter lookup with no output schema, the description covers what is returned (three named fields), the cost, the payment chains, and the auth-free nature. The main remaining gap is the exact response shape/format, which the absent output schema leaves to prose that only summarizes.

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 (empty schema, nothing required), so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies, and the description appropriately spends no words on phantom inputs.

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 a concrete verb and resource — 'Dolphin (POD) price' — and names the three returned fields (live USD price, 24h change, market-cap rank). That is enough to tell it is a single-token price lookup. It does not explicitly distinguish it from sibling patterns like buy_crypto_price or the buy_coin_* family, so it stops short of 5.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance is given relative to the many sibling price tools. The word 'live' implies a real-time use case and 'Paid' signals a cost barrier, but neither is framed as a selection criterion against alternatives such as buy_crypto_price.

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