Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HOLO

Paid. Holoworld (HOLO) 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/HOLO.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations at all, the description carries the full burden and does an unusually good job: it discloses the cost ($0.05 USDC), the accepted payment chains (Base or Solana), the absence of auth/API key, and the failure-billing policy. Not disclosed are rate limits, latency, or what an error response looks like, which keeps it at 4 rather than 5.

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?

Five short fragments, front-loaded with the payment flag before the payload description, then cost, auth, failure policy, and endpoint. Every sentence carries operational information; nothing is repeated from the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 lookup, the description covers everything needed to call it correctly: what is returned, that it costs money and on which chains, that no credentials are required, and that failed calls are free. No material gap remains for a tool of this simplicity.

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 for a 0-param tool is 4. The description correctly implies the symbol is already baked into the endpoint URL, so the agent understands no argument is needed.

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 resource precisely ("Holoworld (HOLO) price") and enumerates exactly what comes back (live USD price, 24h change, market-cap rank), so an agent knows this is a single-token spot quote rather than a market-wide screener. It does not explicitly contrast itself with the mass of sibling lookups (e.g. buy_coin_* or buy_crypto_price), which keeps it just short of a 5.

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?

When-to-use is only implied by the token name — an agent infers "call this if you need HOLO's price." The description does supply real gating context (paid, no account, no API key, failures not charged), which helps the agent decide whether it can call at all, but it never names an alternative tool or states an exclusion condition.

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