Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PAXG

Paid. PAX Gold (PAXG) 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/PAXG.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does well on commerce mechanics (paid, $0.01 USDC on Base or Solana, no account or API key, failed calls not charged, endpoint URL), but says nothing about latency, rate limits, caching, or what an error/empty response looks like.

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?

Front-loaded with 'Paid.' then the payload, then cost, then access constraints, then the endpoint. Every clause adds a fact an agent needs; there is no filler or repetition.

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?

With no annotations and no output schema, the description must cover both the returned data and the access model, and it largely does: it names the three returned fields and the full payment/authorization story. Remaining gaps are response format and failure modes, which are minor for a single-value price lookup.

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 schema is an empty object with zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The description correctly implies the asset is fixed by the tool rather than passed as an argument, which is the only semantic question that matters here.

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?

Names a specific asset (PAX Gold / PAXG) and enumerates exactly what comes back: live USD price, 24h change and market-cap rank. An agent knows precisely what it gets. It does not, however, distinguish itself from buy_crypto_price or the buy_coin_* family, which likely cover overlapping price data.

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 by the token-specific name; there is no statement of when to pick this over buy_crypto_price or another price sibling, nor any preconditions beyond payment. The payment mechanics are spelled out, but the routing decision is left to inference.

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