Skip to main content
Glama

SouthPow crypto & market data

buy_coin_BTRST

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

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

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 discloses substantial behavior: the exact $0.01 USDC charge on Base, no account or API key requirement, no charge for failed calls, and exchange sourcing with a Kraken cross-check. It does not explicitly state that the operation is read-only quote retrieval rather than an asset purchase, nor explain the payment mechanics.

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 dense but efficient, front-loading the paid status and asset before covering metrics, provenance, cost, authentication, failure billing, and the endpoint. Each clause provides useful operational information without unnecessary wording.

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 fixed, zero-parameter endpoint, the coverage of returned data, sources, pricing, authentication, failure behavior, and URL is strong, especially without an output schema. The main remaining gaps are sibling-selection guidance and explicit clarification that this retrieves market data rather than buying BTRST.

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?

There are zero parameters, so the baseline score of 4 applies. The fixed BTRST endpoint reinforces that callers do not need to supply a symbol, dates, 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 identifies a live BTRST/USD market-data resource and enumerates the available price, change, and volume metrics, distinguishing it from other ticker-specific siblings. It lacks an explicit retrieval verb and does not clarify how it differs from the generic 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 Guidelines3/5

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

The BTRST/USD scope implies when to call the tool, but there is no explicit selection guidance or when-not rule. In particular, it does not say whether to prefer this fixed endpoint or buy_crypto_price for BTRST data.

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