Skip to main content
Glama

SouthPow crypto & market data

buy_tok_WOO

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

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

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 provided, the description carries the full burden and does reasonably well: it discloses cost ($0.01 USDC), accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying endpoint URL. It stops short of describing latency, freshness, or the exact response shape, which matters because there is no output schema.

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?

Telegraphic and front-loaded — cost, then payload, then payment mechanics, then endpoint — with no filler sentences. The clipped style ('Paid.' as a standalone fragment) is efficient but slightly rough as prose.

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, annotation-free, output-schema-free paid lookup, the description covers the essentials an agent needs to decide and invoke: what data comes back, what it costs, how to pay, and that failures are free. Return formatting is the only notable omission, and the data fields are already enumerated.

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 implies no arguments are needed (the token and endpoint are baked in), and it adds the one piece of context a caller needs: payment is on Base or Solana.

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 states a concrete resource and payload: 'WOO (WOO) price: live USD price, 24h change and market-cap rank', which is far more specific than the bare tool name. It does not explicitly route the agent among the hundreds of sibling buy_tok_* and buy_coin_* price tools or distinguish itself from buy_crypto_price, so it is clear but not sibling-differentiating.

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?

Leading with 'Paid' and giving the price and payment chains implies the usage context (a paid per-call price lookup for this one token), but there is no explicit statement of when to choose this over buy_crypto_price or the buy_coin_* family. Guidance is implied rather than stated.

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