Skip to main content
Glama

SouthPow crypto & market data

buy_tok_MHYPER

Paid. Midas mHYPER (MHYPER) 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/MHYPER.

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

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 burden and does well: it discloses that the call is paid, the exact price and accepted payment chains, that no account or API key is needed, and that failed calls are not charged. It stops short of describing response format, data freshness/latency, or rate limits, 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 a short, front-loaded block: cost flag first, then what the call returns, then payment/auth terms and the endpoint. Every sentence carries a distinct fact and nothing is padded, though the bare 'https://...' URL is of marginal value to an agent choosing between tools.

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?

There is no output schema, so the description rightly enumerates the returned fields (live USD price, 24h change, market-cap rank) and covers billing and auth. For a zero-parameter, single-asset price tool this is close to sufficient; only pagination/error-shape details are absent, and they are unlikely to matter 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 there is no per-argument semantics to convey and the schema imposes nothing to compensate for. The description usefully confirms the token is fixed by the call itself (MHYPER), so no filtering or identifier input is expected.

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 uses a specific verb-plus-resource framing ('Midas mHYPER (MHYPER) price: live USD price, 24h change and market-cap rank'), so an agent knows exactly what data comes back and for which asset. It does not, however, explain how this differs from the generic buy_crypto_price or the buy_coin_* family that also appear as siblings.

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?

Commercial and access conditions are spelled out ('$0.05 USDC on Base or Solana. No account, no API key'), which tells an agent this is a paid, credential-free single-token price call. There is no explicit when-to-use or when-not-to-use guidance relative to the cheaper/alternative price tools in the sibling list, leaving routing 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