Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HAROLD

Paid. Harold (HAROLD) 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/HAROLD.

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

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?

With no annotations, the description carries the full burden and does well: it discloses the price, accepted chains/currency, absence of auth, and that failed calls are not charged — the risk facts an agent needs before spending money. It omits rate limits and any note on response freshness/latency, so it is strong but not complete.

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?

Roughly two sentences and a URL, front-loaded with the paid flag and the return payload. Every fragment (cost, chains, no-key, no-charge-on-failure, URL) carries information an agent needs; nothing is redundant.

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 paid data lookup with no output schema, the description covers cost, payment rail, auth, failure billing, and the returned fields — enough to call it correctly and judge risk. It could go one step further by describing the response shape (e.g. JSON fields/units) or expected latency.

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. The description correctly signals a parameterless invocation by embedding the token and endpoint in the tool itself rather than requiring 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?

States a specific resource and payload: HAROLD's live USD price, 24h change and market-cap rank, plus the endpoint URL. An agent knows exactly what data comes back. It stops short of distinguishing this from the large family of look-alike siblings (buy_crypto_price, buy_coin_HAROLD), leaving that differentiation implicit in the token name.

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?

The payment context ("$0.05 USDC on Base or Solana", "No account, no API key") tells the agent the preconditions for calling, which is genuinely useful for a paid tool. However there is no guidance on when to prefer this over buy_crypto_price or buy_coin_HAROLD, and no explicit statement that the call is only for the HAROLD token.

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