Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HOLLAR

Paid. Hydrated Dollar (HOLLAR) 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/HOLLAR.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/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 real behavioral facts: it is a paid call, the price is $0.01 USDC, payment rails are Base or Solana, no auth is required, and failed calls are not charged. It omits the response shape, latency, and what the failure modes actually are (e.g. what counts as a failed call), so the payment contract is only partially specified.

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?

Five short clauses, front-loaded with 'Paid' so the cost gate is known before anything else. Every sentence carries signal (asset, fields, price, rails, auth, failure billing, URL). The staccato style is slightly choppy but there is 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, unannotated, no-output-schema price tool, the description covers what the agent most needs: what is returned, what it costs, and how payment works. Since no output schema exists, the brief field list (price, 24h change, market-cap rank) stands in for return-value documentation, which is adequate though not exhaustive.

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 input schema is an empty object with zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies; the description correctly does not waste words on nonexistent parameters and instead front-loads payment details.

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?

States a specific verb (pay for / buy) tied to a named resource, Hydrated Dollar (HOLLAR), and enumerates what the payload contains: live USD price, 24h change and market-cap rank. An agent can distinguish it from the many buy_tok_* siblings because the token is named in both the title of the tool and the description. It does not distinguish itself from the generic buy_crypto_price or buy_coin_* tools, which keeps it off 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?

Gives cost and access context ($0.01 USDC on Base or Solana, no account, no API key, failed calls not charged) which helps an agent decide to call it. However there is no explicit statement of when to prefer this over buy_crypto_price or a buy_coin_* equivalent, and no when-not-to-use guidance. Usage is implied rather than routed.

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