Skip to main content
Glama

SouthPow crypto & market data

buy_coin_THQ

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

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

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 so well: it discloses the payment cost and rail, that no authentication is required, that failed calls are not charged, and that data comes from Coinbase Exchange with a Kraken cross-check. It omits rate limits, latency, and what a failure response looks like, but the core commercial and auth behavior is covered.

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?

The payment caveat is front-loaded as 'Paid.' and every clause carries information: data fields, sources, cost, rail, auth, failure policy, URL. It is telegraphic rather than prose, which suits a zero-parameter call, though the fragment style takes a moment to parse.

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 output schema, the description compensates by listing the returned metrics and their sources, which is the right move. Missing are return format details (JSON structure, timestamps, precision) and failure behavior beyond the no-charge guarantee, but for a zero-parameter price lookup it is nearly sufficient.

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 nothing for the description to disambiguate and the baseline applies. The description correctly signals that no inputs are needed by specifying a fixed URL and fixed price.

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 a specific resource (THQ/USD live price) and enumerates exactly what the data covers: last price, 24h open/high/low, % change, 24h and 30d volume. The verb is left implicit ('Paid.' plus a URL suggests a fetch/purchase), but the resource is unambiguous. It doesn't explicitly differentiate itself from siblings like buy_crypto_price, though the ticker-specific name and description make the distinction obvious.

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?

It establishes context (paid, $0.10 USDC on Base, no account or API key, failures not charged), which tells the agent the preconditions and risk of calling. It does not, however, say when an agent should pick this over buy_crypto_price or how to handle a failed payment, leaving the sibling choice to inference.

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