Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HOT

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

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

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 burden and discharges most of it: it discloses cost ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is needed, and the important failure policy that failed calls are not charged. That last point is genuinely non-obvious behavioral context an agent cannot get from structured fields. It omits rate limits and update frequency, which keeps it below 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.

Conciseness4/5

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

Telegraphic but front-loaded and waste-free: payment flag, payload, price, access model, failure policy, endpoint, in that order. The fragment style ('No account, no API key.') reads as compressed rather than sloppy, and no sentence is redundant. A slightly fuller first sentence naming the tool's role would cost nothing.

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, single-asset price lookup with no output schema, the description covers the essentials an agent needs before spending money: what comes back, what it costs, on which chains, and that failures are free. The remaining gap is the shape of the returned object and the freshness of the quote, which the absent output schema would otherwise have carried.

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; the baseline for a parameterless tool applies. The description instead spends its words on payment and failure semantics, which is the right trade-off.

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 the specific asset (Holo/HOT) and the exact payload: live USD price, 24h change, and market-cap rank. That is a concrete verb-plus-resource statement an agent can match against a request for HOT pricing. It stops short of explicitly distinguishing itself from the many buy_coin_* and buy_crypto_price siblings, so an agent must infer the split from the 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?

Context is implied by the 'Paid.' opener and the per-call price, so an agent knows this is a paid single-asset lookup. But there is no explicit when-to-use or when-not-to-use, no mention of the general buy_crypto_price or buy_coin_HOT alternatives, and no statement about data freshness versus those siblings. The agent is left to infer routing from the ticker in the 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