Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BTW

Paid. Bitway (BTW) 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/BTW.

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

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 solid work: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no account or API key is required, that failed calls are not charged, and it names the response fields (live USD price, 24h change, market-cap rank). Gaps remain around how payment is actually settled (auto-charge? wallet?) and data freshness or rate limits.

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?

It is front-loaded with the most decision-relevant fact ('Paid') and packs pricing, auth, failure policy and the endpoint into a handful of fragments with no filler. The telegraphic fragment style is efficient but slightly flattens hierarchy, making cost and data fields feel equally weighted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, single-endpoint paid quote tool with no output schema, the description covers everything an agent needs: cost, accepted chains/currency, no-auth requirement, non-billing on failure, the literal URL, and the fields returned. Nothing material is missing for a correct invocation decision.

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 and the baseline of 4 applies. The description usefully confirms the token is fixed to BTW rather than passed as an argument, which prevents an agent from looking for a symbol parameter.

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 verb and resource — retrieving the live USD price, 24h change and market-cap rank for Bitway (BTW) — so the agent knows exactly what data comes back. It does not, however, differentiate itself from siblings like buy_coin_* pairs or buy_crypto_price, which likely return overlapping market data; the agent must infer the distinction from the token symbol alone.

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: call this when you need a current BTW quote, and the 'Failed calls not charged' plus '$0.01 USDC' notes imply it is a metered call to be used deliberately. There is no explicit statement of when to prefer it over buy_coin_* or buy_crypto_price, and no prerequisite or exclusion guidance.

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