Skip to main content
Glama

SouthPow crypto & market data

buy_tok_APXUSD

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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden, and it does deliver real behavior: paid at $0.01 USDC on Base or Solana, no account or API key required, and failed calls are not charged. What it omits is the payment mechanics (how the charge is authorized/settled) and response shape or freshness guarantees, which matter for a 0-parameter paid endpoint.

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 'Paid.' then what the call returns, then cost and access terms, then the endpoint URL. Dense and nearly waste-free; the 'apxUSD (APXUSD)' duplication is minor and the raw URL is arguably useful for verification.

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-argument, no-output-schema price lookup, the agent learns cost, payment chains, auth requirements (none), failure billing policy, and the data returned. Slightly incomplete on how payment is actually made and on data freshness, but otherwise sufficient to call confidently.

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 no parameter semantics to explain and the baseline of 4 applies. The description correctly does not waste words restating 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?

The description states a specific resource and payload: live USD price, 24h change, and market-cap rank for apxUSD (APXUSD). The token is unambiguous from the name and body, but it never contrasts itself with adjacent siblings such as buy_crypto_price or buy_stable_apxusd, so an agent must infer the boundary.

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 only implied: an agent is expected to call this when it wants APXUSD pricing. There is no explicit 'use this instead of X' routing, no note on when a general price tool (buy_crypto_price) or the stablecoin metadata tool (buy_stable_apxusd) would be preferable.

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