Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USDH

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does add genuinely useful behavior: this is a paid call at $0.05 USDC payable on Base or Solana, requires no account or API key, and failed calls are not charged. It stops short of stating rate limits, whether payment is handled automatically per call, or what the error/response shape looks like.

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?

Front-loaded with the paid flag and the returned fields, then pricing, then constraints, then endpoint. Nothing is buried, and every clause carries information; the only redundancy is the harmless 'USDH (USDH)' label.

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 paid lookup with no output schema, the essentials are present: what data comes back, the cost, the accepted payment chains, and the no-charge-on-failure policy. What is missing is how the payment actually settles on invocation and whether the listed URL is the call target or just documentation for it.

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 beyond the fact that the symbol and URL are fixed inside the tool. Baseline 4 applies.

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 resource precisely (USDH) and enumerates the exact fields returned: live USD price, 24h change, and market-cap rank. It does not, however, distinguish this tool from the parallel buy_coin_USDH or the generic buy_crypto_price sibling, so an agent cannot tell from the text alone which price endpoint is canonical.

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 explicit when-to-use or when-not-to-use statement, and no alternative is named even though buy_coin_USDH and buy_crypto_price cover overlapping ground. The sentences about payment rail and failure billing describe purchase mechanics, 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