Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OPAIPON

Paid. OpenAI (Ondo Private Market Note) (OPAIPON) 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/OPAIPON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does a good job: it discloses commercial terms ($0.01 USDC), accepted payment chains (Base or Solana), zero auth requirements (no account, no API key), and failure billing policy (failed calls not charged). It stops short of describing response shape, latency, or rate limits, which keeps it from 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?

Front-loads the billing flag ("Paid."), then the purpose, then cost/rails/policy and the endpoint. Every sentence carries operational weight, though the doubled parenthetical asset label ("(Ondo Private Market Note) (OPAIPON)") is slightly redundant and the raw URL is of marginal use to an agent that invokes by tool name.

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, annotation-free price lookup with no output schema, the description covers the essentials an agent needs before spending money: what data comes back, what it costs, which chains to pay on, that no credentials are needed, and that failures are free. Only the concrete response structure is left unspecified, which is a minor gap given the fields are enumerated in prose.

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 no parameters, so there is no argument semantics to explain beyond confirming the call is parameterless; the baseline for zero-param tools applies. The description appropriately spends its words on cost and output content instead of inventing parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (OPAIPON, the Ondo Private Market Note tied to OpenAI) and the exact data returned: live USD price, 24h change, and market-cap rank. The token symbol in the name plus the spelled-out asset identity makes it trivially distinguishable from the hundreds of buy_tok_* siblings.

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 implied by the asset-specific nature: call this when you need OPAIPON pricing rather than another token's. However, it never explicitly says when to prefer it over adjacent tools like buy_crypto_price or the other buy_tok_* variants, nor does it state any exclusions or preconditions.

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