Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BTR

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden and does so well: it declares the tool is paid, the exact cost ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It could add response latency/caching or refresh cadence, but the cost, auth and failure semantics are unusually complete.

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' and then the payload, then pricing and access terms; every clause carries information. The telegraphic fragments ('No account, no API key.') read tersely but nothing is wasted.

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 and no annotations, the description supplies the payload contents, cost, payment rails, auth posture and failure policy, which is enough to call it correctly. The raw endpoint URL is of limited use to an agent and does not substitute for details like data freshness.

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 is 4; the description sensibly spends its words on the returned fields instead, which is the right trade-off for a no-arg tool.

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?

States a specific resource and payload: 'Bitlayer (BTR) price: live USD price, 24h change and market-cap rank.' The symbol in the name plus this enumeration clearly distinguishes it from the many sibling buy_tok_* tools and from buy_crypto_price.

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 by the fixed asset (BTR) and the price model, but the description never says when to prefer this over the generic sibling buy_crypto_price or buy_coin_BTR, nor any when-not conditions such as freshness or rate limits.

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