Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ADI

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

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

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 does real work here: it discloses that the call is paid, the exact price and accepted chains, that no auth is required, that failed calls are free, and the backing endpoint URL. It omits the response shape and any rate limits or payment mechanics (e.g., how the USDC is collected), which keeps it short of a 5.

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 but dense: cost is front-loaded ('Paid.'), followed by payload, price, and terms in four short clauses. The bare endpoint URL at the end is the only questionable element, though it aids debugging.

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, the description covers what matters: what data comes back, what it costs, on which chains, and the failure-charging policy. Return format and payment-collection mechanics remain unspecified, which is a minor gap given the tool's simplicity.

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; the empty schema is fully consistent with a fixed-endpoint lookup. Baseline 4 applies.

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 resource (ADI token) and enumerates the exact data returned: live USD price, 24h change, and market-cap rank, so an agent knows precisely what it buys. It does not explicitly distinguish itself from the generic 'buy_crypto_price' or the many sibling 'buy_tok_*' tools, relying on the tool name to carry that routing.

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?

Payment terms ('$0.05 USDC on Base or Solana', 'No account, no API key') imply this is a pay-per-call lookup, but the description never states when to pick it over buy_crypto_price or another token-price sibling. There are no exclusions or prerequisites stated beyond the cost.

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