Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HSK

Paid. HashKey Platform Token (HSK) 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/HSK.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 so well: it discloses cost ($0.05 USDC), accepted payment rails (Base or Solana), that no account or API key is required, and that failed calls are not charged. Not disclosed: data freshness/refresh cadence and rate limits, which would matter for a live price feed.

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?

Every clause earns its place: billing marker first, then what is sold, then price/rails, then trust signals, then the endpoint. No repetition of the tool name and 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, no-output-schema tool, the definition covers cost, payment, auth, failure handling, and response contents — enough to call it correctly. The remaining gap is operational detail (how payment is actually settled at the endpoint, data freshness), which a first-time agent may still wonder about.

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 and there is no schema semantics to add. The description correctly avoids inventing parameters and instead uses the space to specify the returned fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (HashKey Platform Token / HSK price) and enumerates exactly what is returned: live USD price, 24h change, market-cap rank. An agent can distinguish this from the hundreds of sibling buy_tok_* tools purely from the token symbol and field list.

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 by naming the specific asset, and the leading 'Paid.' plus the $0.05 price gives an agent a cost gate before calling. However, it never states when to prefer this over adjacent siblings (e.g. buy_coin_* or buy_crypto_price) or any preconditions for paying.

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