Skip to main content
Glama

SouthPow crypto & market data

buy_coin_CBETH

Paid. CBETH/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.002 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/CBETH.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 behavioral burden and does substantial work: it discloses that the call is paid, the exact price and settlement chain/asset (USDC on Base), that no account or API key is required, and that failed calls are not charged — all non-obvious facts an agent needs before invoking. It omits response format, latency, rate limits, and whether the Kraken cross-check is a separate field or a validation caveat.

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?

A single dense line, front-loaded with the most decision-relevant fact ('Paid') followed by what you get, what it costs, and the endpoint. Every clause carries information; nothing is padding.

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 no-parameter, no-output-schema price read, the description covers cost, auth, data sources, and the returned fields, which is what an agent needs to call it. Only minor gaps remain: response encoding and whether the two venues are compared or just listed.

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 per the baseline this scores 4; the empty schema and the fully-qualified endpoint URL confirm no input is required. No additional parameter meaning is needed or 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 exact resource (CBETH/USD) and enumerates what is returned: last price, 24h open/high/low, % change, 24h and 30d volume, with source venues (Coinbase Exchange, Kraken cross-check). The symbol in the tool name already separates it from the ~400 sibling buy_coin_* tools, but the description never states that routing rule itself, so it stops short of a 5.

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 context is implied rather than stated: it is a paid endpoint ($0.002 USDC on Base, no account or API key, failed calls not charged), which tells an agent the cost and auth model. However, it never says when to prefer this over the generic sibling buy_crypto_price or whether a single call could serve multiple symbols, and gives no when-not 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