Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HOOKR

Paid. Hookr.fun (HOOKR) 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/HOOKR.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 add real value: it discloses that the call is paid ($0.05 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. That covers cost, auth, and failure policy well. It stops short of describing response shape or staleness guarantees beyond the word 'live', and the endpoint URL is developer-facing rather than agent-usable context.

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?

Front-loaded and short: purpose first, then payment, then access terms, then URL. The telegraphic fragments ('Paid.', '$0.05 USDC on Base or Solana.') read efficiently, though the raw endpoint URL is arguably wasted tokens for an agent that cannot fetch it directly.

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 price lookup, the description supplies the essentials an agent needs before spending money: what data comes back, what it costs, which chains settle payment, and that failures are free. The remaining gap is that the returned field formats and freshness cadence are only implied.

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 of 4 applies. The description correctly implies no inputs are needed by framing it as a fixed per-token lookup.

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 ('Hookr.fun (HOOKR) price') and enumerates exactly what comes back: live USD price, 24h change, and market-cap rank. An agent can tell this returns HOOKR-only price data, though it never explicitly contrasts itself with the many nearby siblings like buy_crypto_price or buy_coin_* variants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not guidance and no named alternative, despite an enormous family of sibling price tools (buy_crypto_price, buy_coin_HOOKR-style tools, buy_pm_* etc.). The only situational information is the payment condition ($0.05 USDC), which tells the agent the cost but not when this tool is the right choice.

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