Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HP

Paid. Hippo Protocol (HP) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/HP.

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

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 supplied, the description carries the full behavioral burden and does a solid job: it discloses that the call is paid ($0.01 USDC), names both accepted payment chains (Base or Solana), states that failed calls are not charged, and gives the underlying endpoint URL. It stops short of describing latency, caching/refresh cadence, or the response shape beyond the field list.

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 billing/mutability caveats are front-loaded ('Paid.') and each subsequent clause adds a distinct fact: what you get, what it costs, how you pay, what is not charged, and where it points. The telegraphic fragment style is efficient but slightly staccato, and the raw URL is arguably filler an agent already derives from the tool binding.

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 parameterless, single-purpose price lookup with no output schema and no annotations, the description covers the essentials an agent needs to decide and pay: subject, returned fields, price, payment rails, and billing-on-failure policy. What is missing — response format details and data freshness — is minor at this complexity level.

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 semantics to explain and the baseline of 4 applies. The description correctly adds no parameter chatter, though it also does not clarify whether the response is scoped to a fixed pair or timestamped.

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 (Hippo Protocol / HP) and enumerates the returned fields: live USD price, 24h change, and market-cap rank. That is clear enough to act on, but with hundreds of near-identical siblings (buy_coin_*, buy_crypto_price) it never states how this token-price tool differs from those, so differentiation rests entirely on the asset symbol in the name.

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 infers you call this when you want the HP price. There is no explicit when-to-use versus buy_coin_HP-style siblings or buy_crypto_price, and no when-not-to-use guidance. The 'no account, no API key' line gives practical access context but not selection guidance.

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