Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BTT

Paid. BitTorrent (BTT) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/BTT.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses that the call is billable, the exact price and payment rails, that no authentication is required, and that failures are not billed. It stops short of describing billing timing, rate limits, or how the charge is settled, but the core cost/safety profile is disclosed.

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?

Five short clauses, each carrying distinct information: paid status, data returned, price and rails, auth requirement, refund policy, endpoint URL. Nothing is repeated and the cost signal is front-loaded in the first word so an agent sees it before anything else.

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 paid price lookup with no output schema, the description covers what is needed to call and pay for it correctly, including the failure-billing policy. The one gap is return shape beyond the three named fields (e.g. whether rank and change are always present), which matters slightly more given there is no output schema to fall back on.

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 no parameter meaning for the description to add; the baseline for a parameterless schema applies. The description correctly implies the asset is fixed by the endpoint rather than passed in, which prevents an agent from hunting for a symbol argument.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (BitTorrent/BTT live USD price) and enumerates the returned data points (24h change, market-cap rank). Against hundreds of buy_tok_<TICKER> siblings that differ only by symbol, it pins the exact asset and the exact payload, so an agent can select it without ambiguity.

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?

It states the commercial terms that govern whether an agent should call it at all: paid at $0.01 USDC on Base or Solana, no account or API key, and failed calls are not charged. What it does not do is name an alternative route (e.g. a free or bundled price source) or give a when-not-to-use condition, which keeps it below a 5.

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