Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OUSG

Paid. Ondo Short-Term U.S. Government Bond Fund (OUSG) 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/OUSG.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the price ($0.01 USDC), the payment rails (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the underlying endpoint URL. Missing rate limits and response shape details beyond the three named fields keep 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?

Very compact and front-loaded: payment status first, then the asset, then the returned fields, then cost/rails/policy, then the URL. Every clause carries information, though the telegraphic fragment style ('Paid.', bare URL) is denser than ideal for parsing.

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 price lookup with no output schema, the description supplies the returned fields, the cost, the payment chains, and the failure-billing policy, which is essentially everything needed to decide and call. Only rate limits and a fuller response contract are absent.

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; baseline 4 applies. The description correctly conveys that the asset is fixed in the tool identity rather than passed as an argument.

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 the exact asset ('Ondo Short-Term U.S. Government Bond Fund (OUSG)') and states the specific payload: live USD price, 24h change, market-cap rank. An agent can tell this is a price lookup rather than a fund-detail or yield lookup. It does not, however, contrast itself with the many nearby variants (buy_coin_ONDO, buy_stable_*, buy_crypto_price), so sibling differentiation is only implicit through the asset name.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no routing against alternatives despite hundreds of near-identical buy_tok_*/buy_coin_* tools. The 'Paid. $0.01 USDC' note hints that cost should factor into selection, but the agent is left to infer that this is the OUSG-specific endpoint rather than being told so.

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