Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BASEDHYPE

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

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

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?

No annotations are present, so the description carries the full burden and does reasonably well: it discloses that the call is paid, the exact price and accepted payment rails, that no authentication is needed, and that failed calls incur no charge. Remaining gaps are rate limits and data freshness, but cost/billing behavior, the riskiest trait for an agent, is explicit.

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 a short, front-loaded block: payment flag first, then what is returned, then cost/auth/failure terms, then the endpoint. Every clause carries information. The raw URL at the end is marginally useful to an agent and could be dropped without loss, which keeps it 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?

With no input schema, no annotations and no output schema, the description must cover the call contract end to end, and it mostly does: it names the three returned fields, the price, the payment chains, the auth model and the failure-billing rule. Only response shape detail and rate limiting are missing, which is acceptable for a single-endpoint price lookup.

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 semantics to explain and the baseline of 4 applies. The description correctly implies the token is fixed by the tool identity rather than passed as an argument.

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 gives a specific verb and resource: it returns BasedHype (BASEDHYPE) live USD price, 24h change and market-cap rank. The purpose is unambiguous. It does not, however, distinguish this from near-identical siblings such as buy_tok_BASED, buy_coin_BASED1 or the generic buy_crypto_price, so an agent must infer the routing from the token ticker 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?

It supplies usable preconditions: $0.05 USDC on Base or Solana, no account or API key required, and failed calls are not charged. What it omits is when to choose this tool over the vast buy_tok_*/buy_coin_* family or buy_crypto_price. Given several hundred near-duplicate siblings, that routing guidance is the missing piece.

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