Skip to main content
Glama

SouthPow crypto & market data

buy_coin_WCT

Paid. WCT/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/WCT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Despite having no annotations, the description discloses the financial side effect, exact charge, payment asset and network, lack of account or API-key requirements, and the policy that failed calls are not charged. It also provides data provenance through Coinbase Exchange and the Kraken cross-check.

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?

The description is compact and front-loaded with the paid status and data purpose, followed by output coverage, provenance, billing, authentication, and endpoint details. Nearly every clause contributes actionable information without unnecessary prose.

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-argument, single-market quote tool, the definition covers the expected data fields, sources, cost, payment network, authentication requirements, and failure-billing behavior. Although there is no output schema, the enumerated metrics provide sufficient expectations for selection and invocation.

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?

With zero parameters, the baseline is 4. The fixed WCT/USD pair and WCT-specific URL reinforce that callers do not need to supply an asset, pair, or other options.

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 clearly identifies paid, live WCT/USD market data and enumerates the last price, 24-hour open/high/low, percentage change, and volume metrics. It does not explicitly use a retrieval verb or distinguish this fixed-asset tool from the broader buy_crypto_price sibling.

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

Usage Guidelines4/5

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

The fixed WCT/USD scope and live-data wording make the appropriate use case clear, while the cost and authentication details help determine whether invocation is acceptable. There is no explicit when-not guidance or routing to an alternative when another coin or a different price source is needed.

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