Skip to main content
Glama

SouthPow crypto & market data

buy_tok_USUAL

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

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

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 that the call is paid ($0.05 USDC), on which chains payment is accepted (Base or Solana), that no account or API key is needed, and that failed calls are not charged. What it omits is data freshness/latency and whether responses are cached, so an agent cannot judge staleness.

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, front-loaded with the payload description before pricing and access terms. Every sentence carries distinct information (data returned, price, payment rails, auth model, failure billing) with 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, annotation-free tool with no output schema, the description covers what is returned at a field level, how to pay, and that auth is unnecessary. The gap is the response shape and value formats (e.g., units for market-cap rank, timestamp), which the agent would only learn by calling.

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 and the baseline is 4. The ticker is baked into the tool identity rather than passed as an argument, which is consistent with the empty schema.

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?

"Usual (USUAL) price: live USD price, 24h change and market-cap rank" names the resource and the three data points returned, which is far more specific than a bare name restatement. It does not explicitly contrast itself with the many sibling buy_coin_*/buy_tok_* price tools, but the ticker embedded in both name and description makes the target asset unambiguous.

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 implied by the data listed (call this when you need USUAL spot price, 24h change, or market-cap rank), and the payment terms make the cost context clear. However, there is no explicit statement of when to prefer this over sibling token-price tools or what happens for other assets.

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