Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HEGIC

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

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

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 burden well: it discloses that the call is paid ($0.05 USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged, which is meaningful retry-safety context. It omits rate limits and how/when the payment is actually settled.

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?

The text is dense and front-loaded, leading with paid/price before cost and access details. The telegraphic, label-style phrasing ('Paid.', '$0.05 USDC on Base or Solana.') is efficient, though the raw endpoint URL is of marginal value to an agent.

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, the description covers what is returned, what it costs, and how access works. The main residual gap is the payment mechanism — it never says whether payment is automatic (e.g. x402) or requires a separate step.

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. Nothing in the text misrepresents the empty input contract.

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?

States a concrete resource (Hegic/HEGIC) and the exact payload (live USD price, 24h change, market-cap rank), so an agent knows precisely what it gets back. It does not, however, explain how it differs from the parallel buy_coin_* family or buy_crypto_price, which cover similar ground.

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 implies usage by naming the data returned and the price/payment rails, but never says when to pick this over buy_coin_HEGIC-style siblings or buy_crypto_price. There are no explicit when-not conditions or stated alternatives, so routing must be inferred 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