Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ORDER

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 it does real work: it declares the tool is paid, names the exact price and payment rails (Base or Solana), states no account or API key is needed, and guarantees failed calls are not charged. Those are the traits an agent most needs before spending money. It stops short of response format, latency, or whether repeat calls are billed each time.

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?

Four short sentences, front-loaded with the paid flag and the payload. Nothing is padded, though the raw endpoint URL is arguably redundant for an agent that only invokes the tool by name.

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 tool with no output schema and no annotations, the description covers the essentials: what data comes back, what it costs, how to pay, and what happens on failure. The remaining gap is that it does not describe the response shape beyond naming three fields, which is a minor omission given there is no output schema to fall back on.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The token is baked into the tool identity and the description confirms it, so no ambiguity is introduced.

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 exact asset and the exact payload: 'Orderly (ORDER) price: live USD price, 24h change and market-cap rank.' That is a specific resource plus an enumerated return set, so an agent knows precisely what it gets. It does not explicitly contrast itself with neighbouring tools such as buy_crypto_price or the buy_coin_* family, which is the only thing keeping 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?

Usage is implied rather than stated: call this when you want the ORDER token's price snapshot. There is no explicit when-not guidance and no named alternative, which matters in a catalogue of hundreds of near-identical buy_tok_* siblings. The '$0.01 USDC, failed calls not charged' lines do help an agent reason about spending, but they are cost terms, not selection guidance.

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