Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HFUN

Paid. Hypurr Fun (HFUN) 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/HFUN.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 a respectable job: it discloses the paid model, exact price and accepted chains, that no account/API key is needed, and that failed calls are not charged — behavior an agent could not infer from an empty schema. It omits response freshness/latency and the shape of the failure response, which would matter for a metered call.

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?

Every clause earns its place: 'Paid.' is front-loaded as the single most decision-relevant fact, then the payload, then cost, prerequisites, billing safety, and the endpoint URL. No filler and no repetition of the tool name.

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 covers what an agent needs: what data comes back, what it costs, how to pay, and that failures are free. The remaining gap is comparative — with ~1000 sibling price tools, it does not say why or when to pick this one over a broader price endpoint.

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 the baseline is 4; there are no arguments whose meaning the description would need to clarify. The description compensates by describing the returned data fields instead.

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 exact resource (Hypurr Fun / HFUN) and enumerates what it returns: live USD price, 24h change, and market-cap rank, so an agent knows precisely what data comes back. It stops short of distinguishing itself from the large family of sibling price tools (buy_crypto_price, buy_coin_*, buy_tok_*) by explaining when this per-token endpoint is preferable to a general price lookup.

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 payment framing ('$0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged') tells the agent the cost and lack of prerequisites, which is real usage context for a pay-per-call tool. However, there is no explicit statement of when to use this versus buy_crypto_price or another sibling, nor any exclusion or prerequisite guidance beyond payment.

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