Skip to main content
Glama

SouthPow crypto & market data

buy_tok_SHFL

Paid. Shuffle (SHFL) 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/SHFL.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations present, the description carries the load and does it well: it discloses that the call is paid, the exact price ($0.05 USDC), accepted chains (Base or Solana), no account or API key requirement, and that failed calls are not charged. Missing is any statement of rate limits, latency, or how a payment failure surfaces to the caller.

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?

Three short sentences and a URL, front-loaded with the paid flag and the returned fields. Every clause earns its place — cost, chains, auth, refund policy — with no restatement of 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 zero-parameter, no-annotations, no-output-schema tool, the definition covers what an agent needs: what data comes back, what it costs, how payment works, and that failures are free. The only gap is the response payload shape, which matters somewhat since no output schema exists.

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; there is nothing for the description to disambiguate. The description correctly signals a no-input invocation by providing the fully qualified endpoint URL instead of arguing about parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-and-resource pair: a paid call that returns SHFL's live USD price, 24h change and market-cap rank. The ticker is named explicitly, which is exactly what distinguishes it from the hundreds of near-identical buy_tok_* siblings, and the returned fields are enumerated rather than left generic.

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?

Implied usage is clear (call it when SHFL price data is needed), and the payment constraints are stated. However, it never names alternatives such as buy_crypto_price or a buy_coin_* variant for the same asset, and gives no when-not-to-use guidance or indication of data freshness/caching.

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