Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BIGTIME

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

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

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 burden and does a solid job: it discloses the pay-per-call model ($0.002 USDC on Base), that no account or API key is needed, that failed calls are not charged, and the upstream data sources (Coinbase Exchange with Kraken cross-check). It does not mention rate limits, latency, or what a failure response looks like, which keeps it below a 5.

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?

Roughly four telegraphic sentences with zero filler, front-loaded with the single most decision-relevant fact ('Paid') followed by what the data contains, then cost and access terms. Every clause carries information an agent needs before calling.

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-argument, no-output-schema endpoint this covers purpose, returned fields, price, access requirements, failure billing, and data provenance — enough to invoke it correctly. Minor gaps remain around response shape and error semantics, but those are largely outside what a no-param price feed needs.

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; baseline for a 0-param schema is 4. The description wisely spends its space on return fields and cost instead of inventing parameter detail.

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 pins down a specific resource — the BIGTIME/USD pair — and enumerates exactly what is returned (last price, 24h OHLC, % change, 24h and 30d volume). It does not explicitly name how it relates to the ~400 sibling buy_coin_<TICKER> tools, but the pair naming makes the distinction obvious without opening the schema.

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 is implied rather than stated: the tool fetches live BIGTIME price data, and the 'Paid' framing plus the $0.002 USDC cost signals this is a paid call. There is no explicit when-to-use/when-not guidance and no pointer to alternatives such as buy_crypto_price or other ticker variants.

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