Skip to main content
Glama

SouthPow crypto & market data

buy_coin_GTC

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 disclose real behavior beyond the schema: it is paid ($0.002 USDC on Base), requires no account or API key, does not charge failed calls, and even exposes the endpoint URL. It omits how payment is actually transacted (wallet/x402 flow), any rate limits or latency, and whether the charge occurs before or after a successful response — significant gaps for a paid tool.

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.' — the most decision-relevant fact — followed by payload, pricing, prerequisites, and endpoint in a single dense block with no wasted sentences. The telegraphic style and trailing bare URL are slightly rough but every clause carries information.

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 tool with no output schema, the description compensates well by enumerating the returned fields and naming the upstream data sources. What is missing is the payment mechanics for a paid endpoint, which is the main operational unknown an agent would face before calling it.

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 the baseline is 4; there is nothing for the description to clarify beyond confirming the symbol is fixed to GTC/USD. It does implicitly confirm no symbol or currency argument is needed, which matches the empty schema.

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 and payload: 'GTC/USD live: last price, 24h open/high/low, % change, 24h and 30d volume', plus upstream sources (Coinbase Exchange, Kraken cross-check). It never states the verb explicitly (return/fetch) and never explains that 'buy' means paying for the data rather than buying the token, so an agent must infer the action from the price and $0.002 fee.

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?

There is no when-to-use or when-not-to-use guidance and no reference to any alternative such as buy_crypto_price or the other buy_coin_* tools. The stated conditions ('No account, no API key', 'Failed calls not charged') describe purchasing terms, not selection criteria, so the agent gets no help choosing this over a sibling.

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