Skip to main content
Glama

SouthPow crypto & market data

buy_tok_FROGGIE

Paid. Froggie (FROGGIE) 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/FROGGIE.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/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 so well: it discloses the tool is paid, the exact cost and accepted payment chains, that no account or API key is needed, and that failed calls are not charged — the failure-billing policy being a genuinely valuable detail an agent cannot infer. It also gives the endpoint URL for verification.

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 cost and payload, then payment rails, auth, failure policy, URL. Sentence fragments keep it short, though 'Paid.' is redundant with the '$0.05 USDC' sentence and the raw URL is of marginal value to an agent that invokes the tool rather than fetches it.

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 zero-param, single-purpose paid endpoint this covers the essentials: what comes back, what it costs, how payment/auth works, and failure billing. Without an output schema it could have specified the response shape more concretely (fields, units for market-cap rank), which is the only real gap.

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; the description correctly implies no inputs are needed and instead pins the resource (FROGGIE) in the description itself. There is no parameter meaning left to add.

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?

States a specific resource (Froggie / FROGGIE) and exactly what it returns: live USD price, 24h change, market-cap rank. The verb is only implied by the 'buy_' prefix and the 'Paid.' marker rather than spelled out, and nothing distinguishes it from the parallel buy_coin_FROGGIE / buy_crypto_price families, so it stops short of a 5.

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?

Payment terms ($0.05 USDC on Base or Solana) implicitly tell the agent this is for single-token price lookups, but there is no explicit when-to-use or when-not guidance and no named alternative (e.g., buy_crypto_price or buy_coin_*). Usage must be inferred from the token name.

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