Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BASED

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is required, and that failed calls are not charged. That failure/billing policy is exactly the kind of behavior an agent needs before spending money; only rate limits and latency expectations are 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?

It is short and front-loaded: payment status first, then the data returned, then price/payment rails, then the failure policy, then the URL. Every sentence carries information; the raw URL is slightly out of place but plausibly serves as an endpoint reference.

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 price endpoint, the description covers the essentials: what data comes back, what it costs, how to pay, and that failures are free. Only the response shape details (units, precision, staleness of the 'live' price) are left implicit.

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 the schema has nothing to explain and the baseline of 4 applies. The description correctly adds no parameter noise and instead spends its words on cost and output content.

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 resource (the BASED token) and enumerates exactly what is returned: live USD price, 24h change and market-cap rank. It is clear what the tool does, but it does not distinguish itself from near-neighbours such as buy_coin_BASED1, buy_tok_BASEDHYPE or the generic buy_crypto_price, leaving the agent to guess why one is preferred.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative among the hundreds of price/token siblings. The cost and payment details help an agent decide whether it can afford the call, but nothing tells it when this endpoint is the right choice over buy_crypto_price or buy_coin_*.

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