Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CBK

Paid. Cobak (CBK) 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/CBK.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/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 well: it discloses that the call is paid, the exact price ($0.01 USDC), the accepted payment chains (Base or Solana), that no credentials are required, and that failed calls are not charged. It does not mention rate limits, latency, or error conditions beyond the no-charge guarantee.

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?

Five short fragments, front-loaded with the cost flag and the resource, then price, payment, auth, billing policy, and endpoint. Every clause carries information an agent needs before calling a paid endpoint; nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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, the description supplies the returned fields, cost, payment rails, credential requirements, billing behavior on failure, and the raw endpoint URL. An agent has everything needed to decide and invoke.

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 there is no parameter meaning to convey and the baseline of 4 applies. The description correctly implies a fixed, parameterless lookup for a single hard-coded asset and endpoint.

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 the exact resource (Cobak/CBK) and the precise payload: live USD price, 24h change, market-cap rank. The token-specific name plus the enumerated return fields make it distinguishable from the hundreds of sibling buy_tok_* tools without opening any schema.

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 token-specific name and the quoted price, but there is no explicit statement of when this is preferable to buy_crypto_price or a buy_coin_* sibling, and no exclusions. The prerequisites that are stated (no account, no API key) are helpful but are not selection guidance.

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