Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HEMI

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

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

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 burden, and it does disclose the non-obvious parts: the call costs $0.05 USDC on Base or Solana, requires no account or API key, and failed calls are not charged. That payment and failure-billing detail is exactly the kind of behavior annotations would otherwise supply. It stops short of stating response format, latency, or rate limits.

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?

Roughly three sentences, front-loaded with 'Paid.' so the agent learns the cost model before anything else. Every clause earns its place: payload fields, price and payment rails, auth, failure billing, endpoint URL. No filler.

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, zero-annotation tool with no output schema, the description does the heavy lifting: it names the returned fields and the commercial terms. What remains uncovered is response structure/shape and data freshness, which an agent would only discover by calling.

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?

There are zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly adds nothing parameter-related and instead spends its words on cost and payload.

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 states a specific resource and payload: HEMI's live USD price, 24h change, and market-cap rank. That is far more than a restatement of the name. It does not, however, point at any sibling (e.g. buy_crypto_price or the buy_coin_* family) for a generic or alternative query, so differentiation rests entirely on the token symbol embedded in the name.

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 implied rather than stated: an agent can infer 'call this to get HEMI price,' and the 'Paid / $0.05 USDC' framing signals a costed single-asset lookup. There is no explicit when-to-use versus buy_crypto_price, no guidance about when not to call, and no note about caching or freshness that would help an agent decide among repeated calls.

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