Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ARDR

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

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

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, the description carries the full burden and does well: it discloses a paid, metered operation, the exact price and accepted payment chains, that no credentials are required, and that failed calls are not billed. It stops short of explaining the payment flow (e.g. how USDC is charged per request) or any rate limits.

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?

Front-loaded with the payoff (what data) and then the cost/access terms, with no filler; the trailing raw URL is largely redundant with the tool name but is short. Fragmented phrasing is efficient rather than confusing.

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-param, no-annotations, no-output-schema paid endpoint, the description covers cost, payment rails, auth requirements, failure billing, and returned fields — everything an agent needs before paying. It only lacks a note on payment mechanics or how to distinguish it from the sibling coin-price tools.

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 reinforces this by explicitly stating no account or API key is needed, confirming a parameterless call. Nothing further is required.

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 specific resource (Ardor/ARDR live USD price) and enumerates the returned fields (24h change, market-cap rank), so an agent knows exactly what data it buys. It does not differentiate itself from the near-identical sibling buy_coin_ARDR, which an agent would have to guess between.

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?

It gives practical invocation context (no account, no API key, $0.05 USDC on Base or Solana, failed calls not charged) that implies when it is usable, but never states when to prefer it over buy_coin_ARDR or buy_crypto_price, nor any exclusions.

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