Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HUMA

Paid. Huma Finance (HUMA) 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/HUMA.

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

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, the description carries the full burden and does a solid job: it discloses that the call costs $0.01, the payment rails (USDC on Base or Solana), that no account or API key is needed, and that failed calls are not charged. It omits rate limits and the response shape, which keeps it from a 5.

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?

It is dense and front-loaded, with cost, payload, payment terms and URL in a few short fragments. The telegraphic style ('Paid.', 'No account, no API key.') is efficient but slightly choppy, so it falls just short of ideal structure.

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 call, the description supplies the return contents (price, 24h change, market-cap rank), the cost, the payment networks, and the failure policy — enough to call it correctly. Only rate-limit/response-format detail is missing, which is minor here.

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 the baseline is 4; there is nothing in the input schema to explain and the description correctly does not invent parameter detail. The endpoint URL conveys the asset identity that would otherwise be a parameter.

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 and the exact payload: 'Huma Finance (HUMA) price: live USD price, 24h change and market-cap rank.' An agent can tell exactly what it gets. It does not, however, differentiate itself from the many sibling price tools (buy_coin_*, buy_crypto_price), so it stops short of a 5.

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?

The 'Paid' flag plus '$0.01 USDC on Base or Solana' gives the agent a cost/eligibility signal, which implicitly frames when to use it. But there is no explicit when-to-use or when-not-to-use guidance and no pointer to an alternative price source for the same asset, leaving the selection decision to inference.

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