Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HALO

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 burden and does well: it discloses that the call is paid, the exact cost ($0.01 USDC), accepted payment chains (Base or Solana), that no account or API key is needed, and that failed calls are not charged — the last being non-obvious and materially useful for retry decisions. It stops short of rate limits, latency expectations, or the response format, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the single most important qualifier ("Paid."), followed by what is returned, then cost, then prerequisites, then the endpoint. Every clause is load-bearing and there is no filler.

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 price lookup with no output schema and no annotations, the description supplies the essentials: returned fields, price, payment rails, authentication needs, failure charging policy, and the raw URL. The remaining gap is the precise response shape, which with no output schema the agent can only infer from the one-line field list.

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 meaning to add and the baseline of 4 applies. The description correctly implies a fixed, fully-qualified request (asset baked into the path) rather than suggesting any caller-supplied input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact asset (Halo / HALO) and enumerates the three data points returned: live USD price, 24h change, and market-cap rank. Against a sibling set of hundreds of near-identical buy_tok_<SYMBOL> tools, this is precisely the differentiation an agent needs to pick the right one without opening a schema.

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?

Implicit usage is clear (call this when you need the HALO spot price), and the payment prerequisites are stated. However, it gives no explicit routing guidance versus generic alternatives such as buy_crypto_price or the buy_coin_* family, nor any statement about when this tool is a poor choice (e.g., for non-HALO assets, or for historical data).

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