Skip to main content
Glama

SouthPow crypto & market data

buy_tok_CHR

Paid. Chromia (CHR) 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/CHR.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the burden and does reasonably well: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no credentials, and that failed calls are not charged. It omits rate limits, latency, and data refresh frequency, which matter for a live-price endpoint.

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?

Front-loaded with 'Paid.' followed by what data is returned, then cost, then access requirements, then the URL — every clause carries information. The telegraphic fragment style is efficient but slightly less readable than complete sentences.

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, the description covers return contents, pricing, payment rails, auth needs, and failure billing, which is close to everything an agent needs to decide and call. The remaining gap is data freshness and any rate/usage limits.

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?

There are zero parameters and 100% schema coverage, so the baseline of 4 would normally apply, but the description adds no meaning beyond the schema here because there is nothing to add. The coin is hard-coded in the endpoint, which is worth noting but not a parameter concern.

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?

States the specific resource (Chromia/CHR) and enumerates the returned fields (live USD price, 24h change, market-cap rank), so the agent knows exactly what it gets. It does not, however, distinguish itself from the very similar sibling buy_coin_CHR or from buy_crypto_price, which is a notable gap in a namespace this dense.

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?

The description gives prerequisites ('no account, no API key') and cost, but no explicit when-to-use guidance and no comparison against the near-identical buy_coin_CHR or the general buy_crypto_price tool. The agent must infer selection from the name 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