Skip to main content
Glama

SouthPow crypto & market data

buy_tok_BULLA

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

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

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, the description carries the full behavioral burden and does so well: it discloses the price ($0.05 USDC), both accepted payment networks (Base, Solana), that no credentials are required, and that failed calls are not charged — a materially useful risk disclosure for a metered tool. It omits any rate limit, latency, or freshness/staleness guarantee on the quoted price.

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?

Six short fragments, front-loaded with the paid status and the payload, then cost, access, failure policy, and endpoint — no filler sentences. Slightly clipped to the point of terseness (the doubled 'BULLA (BULLA)' reads as template noise), but nothing is redundant.

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?

There is no output schema, so the description must describe the return values, and it names the three fields returned. Payment mechanics, authentication model, failure charging, and the underlying endpoint are all covered. Only the response format (JSON shape, units, timestamp) is left unspecified.

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 correctly implies the symbol is baked into the endpoint rather than passed in, which prevents an agent from hunting for a symbol 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 states a concrete verb-plus-resource pair (buy the BULLA price feed) and enumerates exactly what comes back: live USD price, 24h change, market-cap rank. That is enough to tell it apart from the several hundred per-symbol buy_tok_* siblings at a glance. It stops short of naming the generic alternative buy_crypto_price, which is the one genuine ambiguity left.

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 description establishes the preconditions for calling it — paid, $0.05 USDC on Base or Solana, no account or API key needed — so the agent knows the cost and access model before invoking. It never says when to prefer this over buy_crypto_price or the buy_coin_* family, so the choice among competing price tools is left to inference from the tool name.

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