Skip to main content
Glama

SouthPow crypto & market data

buy_coin_COW

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

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

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 well: it discloses the paid model ($0.10 USDC on Base), the absence of auth, that failed calls are not charged, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It omits rate limits, latency, and response shape, but the core cost and safety-relevant traits are all stated.

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?

Very tight: 'Paid.' is front-loaded, then the data fields, then cost/auth/failure terms, then the endpoint URL. Every clause carries information, though the telegraphic style and abbreviations (% change) are slightly terse.

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?

With no annotations and no output schema, the description must define both behavior and return content, and it does: it enumerates the metrics returned and names the data sources. What's missing is error behavior beyond billing and rate or freshness limits, which would matter for an agent planning repeated calls.

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 and the schema is empty, so the baseline applies and no parameter explanation is needed. The description usefully spends its words on output content and cost instead.

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 states a specific resource and scope: live COW/USD price data with named fields (last price, 24h open/high/low, % change, 24h and 30d volume). It differentiates itself from the hundreds of buy_coin_<TICKER> siblings by pinning the asset pair. However, the tool name suggests a purchase/order action while the description describes a paid read-only data lookup, a mismatch the description has to repair.

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?

The description implies usage (fetch COW/USD spot data) and gives decision-relevant context like the $0.10 cost and no account/API key requirement. It never says when to choose this over a sibling such as buy_crypto_price or when not to use it, so an agent must infer the trade-off from price 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