Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HEZ

Paid. Hermez Network (HEZ) 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/HEZ.

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

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 behavioral burden and does real work: it discloses the paid nature, the exact price ($0.05 USDC), accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. It stops short of stating rate limits, the payment protocol, or response freshness/delay.

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?

The payload is front-loaded with 'Paid.' and then packed into a few telegraphic segments: what you get, what it costs, terms, endpoint URL. Every element is load-bearing; the only minor nit is that the raw URL and pricing sit mid-flow rather than being clearly separated into cost-vs-output sections.

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 tool with no output schema and no annotations, the description compensates well by enumerating the returned fields and the payment/error terms. What an agent still lacks is transport detail (response format, latency, how payment is settled), but nothing essential to deciding or calling it is missing.

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; the baseline of 4 applies. The schema is empty and fully described, and the description correctly spends no words on arguments.

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 a specific verb-less but unambiguous resource ('Hermez Network (HEZ) price') and enumerates the three returned fields (live USD price, 24h change, market-cap rank). It is clearly distinguished from the hundreds of sibling buy_coin_/buy_tok_ tools by the asset symbol, though it never explicitly contrasts itself with the generic buy_crypto_price sibling.

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 only implied: the reader infers this is the tool to call when HEZ price data is needed. There is no explicit when-to-use/when-not statement and no named alternative (e.g., buy_crypto_price) for the agent to choose against, so selection guidance is left to the token symbol in the name.

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