Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HUNT

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

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

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 present, the description carries the full load and does so well: it discloses that the call is paid, the exact price ($0.05 USDC), accepted chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of rate limits, payment mechanics, or error behavior beyond the 'not charged' note.

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?

Five short sentences, front-loaded with purpose and followed by cost, auth, billing policy and URL — no filler. The only minor waste is slight redundancy between the leading 'Paid.' fragment and the later '$0.05 USDC' cost statement.

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, no-output-schema endpoint, the description gives everything needed to invoke it: what it returns, what it costs, how to authenticate (nothing), and where it points. Missing only rate limits and the shape of the paid-call failure path, which are secondary for this tool class.

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; baseline 4 applies. The description instead spends its words on return fields and billing, which is the right allocation for a parameterless endpoint.

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 resource (Hunt/HUNT) and the exact payload: live USD price, 24h change and market-cap rank. It does not, however, distinguish itself from adjacent siblings such as buy_crypto_price or buy_coin_HNT-style tools, leaving the agent to infer that this is the token-specific variant.

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?

Usage is only implied: an agent can infer it should call this when it needs HUNT price data, and the 'Paid' / '$0.05 USDC' line signals cost. There is no explicit when-to-use versus alternatives (e.g. the generic crypto price tool) and no statement of when not to call it.

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