Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CSPR

Paid. Casper Network (CSPR) 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/CSPR.

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

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 zero annotations, the description carries the full burden and does substantial work: it declares the tool is paid, the exact price and accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged — the key risk facts for an agent that may trigger a payment. Missing are the response shape (no output schema exists) and any statement on quote freshness, cache TTL, or rate limits.

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?

Roughly 40 words of telegraphic clauses, each carrying a distinct fact: what it returns, price, payment chains, auth, billing on failure, and the endpoint URL. Front-loaded with the payload description and then the cost, which is the right priority order. Slightly fragmentary style ('Paid.' 'No account, no API key.') reads as notes rather than prose but wastes nothing.

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 paid data endpoint with no annotations and no output schema, the definition covers the decisions an agent must make: is it relevant (CSPR price fields), what does it cost, how is it paid, and does failure incur charges. The remaining gap is return-value detail — units, precision, timestamp on the 'live' price — which normally would fall to an output schema that this tool lacks.

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 schema has nothing to explain and the baseline of 4 applies. The description correctly implies a fixed, fully-qualified request (the CSPR symbol and URL are baked in), so an agent will not go hunting for a symbol argument that does not exist.

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?

Names the specific resource (Casper Network / CSPR) and exactly what is returned: live USD price, 24h change, market-cap rank. That is well beyond a tautology and lets an agent distinguish CSPR quotes from the hundreds of other buy_tok_* tickers by suffix. It loses a point only because it never contrasts itself with the generic buy_crypto_price or the parallel buy_coin_* family, so scope relative to siblings is inferred rather than stated.

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 implied by the endpoint nature — call this to get a CSPR price quote — and 'Paid... $0.05 USDC' signals the cost trade-off an agent should weigh. But there is no explicit when-to-use/when-not, no mention of the cheaper non-paid alternatives like buy_crypto_price or free crypto endpoints, and no guidance on caching/reuse to avoid repeated charges.

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