Skip to main content
Glama

SouthPow crypto & market data

buy_tok_H

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

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

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, the description carries the full load and does well: it discloses the paid model, the exact price ($0.01 USDC on Base or Solana), no account or API key required, and that failed calls are not charged — key cost/risk context an agent needs before spending. It stops short of stating read-only/idempotency or the response shape, which is the main remaining gap.

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?

Five short sentences: payment flag first, then what is returned, then cost and rails, then auth, then billing policy and endpoint. No filler and nothing important is deferred.

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-param, no-output-schema endpoint the description covers what data comes back, how it is paid for, and where the request goes — enough to call correctly. Only the response format and refresh semantics are left unstated, which is acceptable given the fixed asset.

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 what the schema already conveys. Baseline 4 applies; the description correctly adds that the asset is fixed (H) rather than caller-specified.

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 verb+resource: live USD price, 24h change and market-cap rank for Humanity (H). The scope is unambiguous even buried among hundreds of buy_tok_* siblings, though it never explains how it differs from buy_coin_H or buy_crypto_price.

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 context is implied by naming the exact data points the caller gets, and payment logistics imply 'use this when you need H price'. But there is no explicit when-to-use / when-not, and no routing to an alternative for the same asset (buy_coin_H) or for broader price lookups.

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