Skip to main content
Glama

SouthPow crypto & market data

buy_tok_PREOPAI

Paid. OpenAI (Republic Pre-IPO) (PREOPAI) 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/PREOPAI.

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

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?

With no annotations present, the description must carry the full behavioral burden, and it does disclose meaningful operational facts: cost ($0.01 USDC), accepted chains (Base or Solana), no account or API key required, and that failed calls are not charged. It does not cover rate limits, data freshness, or response shape, so the disclosure is solid but incomplete for an unannotated tool.

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?

Nearly every clause earns its place: asset, payload, price, payment rails, auth posture, billing policy. The parenthetical naming and trailing raw URL make it slightly dense/run-on rather than crisply front-loaded, but there is little waste.

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?

No output schema and no annotations exist, so the description must describe returns, and it lists the three fields produced. Combined with cost and chain details, that is sufficient for an agent to invoke it correctly; only freshness/latency expectations are unaddressed.

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 schema semantics to add; baseline 4 applies. The description correctly signals that no inputs are needed, since the asset is baked into the endpoint URL.

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 asset (OpenAI Republic Pre-IPO, ticker PREOPAI) and enumerates exactly what is returned: live USD price, 24h change, and market-cap rank. That is enough to separate it from the hundreds of buy_tok_* siblings, though the action itself (fetch a price) is implied rather than stated with an explicit verb.

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 can infer it should call this for PREOPAI price data. There is no statement of when to prefer it over neighbors like buy_crypto_price or other buy_tok_* tools, though the payment and no-account prerequisites do give practical call context.

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