Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HANDY

Paid. Handy (HANDY) 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/HANDY.

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

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?

No annotations are supplied, so the description must carry the full behavioral burden, and it does substantially: it flags 'Paid' up front, states the exact cost ($0.01 USDC on Base or Solana), confirms no account or API key is needed, and clarifies failed calls are not charged. The remaining gap is response format and freshness/latency, which are not stated.

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?

Six short fragments, each earning its place: payment flag first, then purpose, then cost, then auth, then billing guarantee, then endpoint. Nothing is repeated and the most decision-relevant facts (paid, how much) are front-loaded.

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?

With no output schema, the description must convey what comes back, and it does by listing the three fields returned. Access mechanics, cost, and billing-on-failure are all covered. It could be stronger by noting the response format or data freshness, but an agent has enough to invoke it correctly.

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 parameter meaning to add and the baseline of 4 applies. The description correctly implies the token is fixed by the tool itself rather than passed as an argument.

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 (Handy/HANDY) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. That is a concrete verb+resource statement an agent can act on. It stops short of differentiating from the near-identical generic siblings (buy_crypto_price, buy_coin_HANDY), so it is clear but not sibling-differentiated.

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: an agent infers it should call this when it wants HANDY pricing specifically. There is no explicit when-to-use, no when-not-to-use, and no named alternative such as buy_crypto_price for general price lookups. The payment and access details are clear but they describe cost, not selection guidance.

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