Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BORA

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and does most of it: it discloses the cost ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and the important failure policy that failed calls are not charged. The remaining gap is the mechanics of payment settlement and the response format, which are left unstated.

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?

Compact and front-loaded: the paid flag and what is returned come first, commercial terms follow. The trailing raw "URL https://..." is redundant metadata that adds little for an agent, keeping this just short of a 5.

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, no-output-schema paid lookup, the description covers the data returned, the price, the payment rails, and the no-charge-on-failure policy, which is what an agent needs before spending money. It stops short of explaining how the $0.05 payment is actually executed or what the response payload looks like.

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 beyond the token identity, which it already pins to BORA. Baseline of 4 applies for a parameterless tool.

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?

States a specific resource and the exact fields returned: "BORA (BORA) price: live USD price, 24h change and market-cap rank." That is clear enough for an agent to know what it gets. It does not acknowledge the crowded token/price families among its siblings (buy_crypto_price, buy_coin_*), so the scoping is clear but not differentiated.

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 intended use (fetch BORA spot price and 24h data) is implied by the content listing, and the "No account, no API key" line removes a common prerequisite. However, there is no explicit when-to-use versus alternatives such as buy_crypto_price or a general market-data tool, and no guidance on when a paid single-token call is preferable to a cheaper sibling.

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