Skip to main content
Glama

SouthPow crypto & market data

buy_tok_C

Paid. Chainbase (C) 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/C.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and largely meets it: it discloses that the call is paid, the exact cost ($0.01 USDC), the payable chains (Base or Solana), the absence of account or API key requirements, and that failed calls are not charged. That is exactly the behavioral context an agent needs before spending money; it only omits whether the result is cached or how fresh the 'live' quote is.

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?

Six short fragments, front-loaded with the payment flag and then the resource and return fields, then cost, auth, and endpoint. Nothing is redundant and the endpoint URL is useful for verification.

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 paid price lookup, the description covers what it returns, what it costs, where to pay, and what auth is not needed. The only missing piece is return format/serialization and quote freshness, which the agent cannot learn from any structured field here.

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 per-argument meaning to convey and the baseline of 4 applies. The token identity is baked into the tool name and description rather than passed as an argument, and the description correctly signals that no input is expected.

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?

The description names the paid resource precisely: 'Chainbase (C) price: live USD price, 24h change and market-cap rank', so an agent knows it returns price data for one specific token. The gap is sibling differentiation — with hundreds of buy_tok_* and buy_coin_* tools present, the description never explains how buy_tok_C relates to buy_coin_*C98-style tools or to buy_crypto_price, and the bare ticker 'C' is easy to confuse with CACAO/CAW/CRV-family entries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement and no named alternative; the agent is left to infer that buy_tok_C is the per-token price endpoint versus the generic buy_crypto_price. The pricing and 'failed calls not charged' lines describe the transaction, not the selection decision.

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