Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CRED

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

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

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, the description carries the full burden and does real work: it discloses the payment model ($0.01 USDC on Base or Solana), that no account or API key is needed, and the important billing policy that failed calls are not charged. It omits response shape, latency, and whether the price is cached or real-time beyond the word 'live'.

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 clauses, front-loaded with the critical 'Paid' qualifier, then what you get, then cost and access terms, then the raw URL. Nothing is padded and no sentence is redundant.

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-output-schema tool this covers the essentials: what data comes back, that it costs money, how to pay, and that failures are free. The main gap is return format — an agent cannot tell whether it receives JSON, a number, or a formatted string — but that is a modest omission for a single-value lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics to add and the baseline applies. The description correctly implies a parameterless call by stating the asset is fixed in the endpoint URL, which is mildly useful confirmation.

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 exact asset (Credible Finance / CRED) and enumerates the payload: live USD price, 24h change, market-cap rank. That is specific enough to separate it from the hundreds of sibling buy_tok_* endpoints. It stops short of naming the nearest alternative (e.g. buy_crypto_price) so an agent still has to infer routing from the ticker suffix.

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?

Use is implied by the token name and payload description, and the 'Paid' prefix plus the price tag make the cost condition explicit. However there is no explicit when-to-use / when-not statement or comparison against generic price tools such as buy_crypto_price, so selection relies on the naming convention alone.

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