Skip to main content
Glama

SouthPow crypto & market data

buy_tok_H2O

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does a solid job: it discloses that the call is paid ($0.01 USDC on Base or Solana), requires no account or API key, and that failed calls are not charged. It does not say what a successful response looks like structurally or whether the price is cached, but the commercial and access behavior is unusually well covered.

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?

Short, front-loaded and scannable: payload first, then price, then access terms, then endpoint. The one blemish is the redundant 'H2O (H2O)' and the raw URL, which is marginally useful but not wasteful.

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 endpoint, the description supplies the information an agent actually needs before calling: what data returns, what it costs, how to pay, and that failures are free. Only the response shape and freshness are unspecified, which is a minor gap given there is no output schema to lean on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which normally sets a baseline of 4, but there is nothing parameter-like for the description to illuminate. It does implicitly confirm the call is fully self-contained (no asset symbol or quote currency needed), which is worth a little, landing at 3.

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 specific resource and the exact payload: live USD price, 24h change and market-cap rank for H2O. The resource is unmistakable, but with ~700 near-identical siblings (buy_coin_*, buy_tok_*, buy_crypto_price) it never says how this differs from a generic price tool, so an agent must infer selection from the name alone.

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: fetch this when you need an H2O spot quote. There is no explicit when-to-use, no 'prefer this over buy_crypto_price when...' guidance, and no note on how stale the quote may be. The payment and access notes are helpful context but are not usage routing.

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