Skip to main content
Glama

SouthPow crypto & market data

buy_tok_ONYC

Paid. OnRe Tokenized Reinsurance (ONYC) 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/ONYC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it declares the tool is paid ($0.01 USDC), names both accepted payment rails (Base or Solana), states no account or API key is required, and clarifies that failed calls are not charged — a critical cost-safety fact an agent cannot otherwise know.

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 and dense: payment status, what it returns, cost, rails, auth, billing policy, all in a few short fragments with no filler. The trailing raw endpoint URL is marginally useful to an invoker and the only phrase that isn't strictly needed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe return values — and it lists the three returned fields explicitly. Combined with pricing, payment rails and billing-on-failure behavior, an agent has everything needed to decide and call correctly.

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 has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description implicitly confirms the token is fixed by the endpoint rather than passed as an argument, which is a useful clarification.

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?

Names the specific resource (OnRe Tokenized Reinsurance / ONYC) and enumerates exactly what comes back: live USD price, 24h change and market-cap rank. Against a sea of buy_tok_* siblings, the token identity in the description is what lets an agent confirm this is the ONYC price feed rather than a generic crypto price call.

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 rather than stated: this is a price lookup for a single token, and an agent can infer that. However, the description never routes the agent away from adjacent siblings such as buy_yields_token_onyc (yield data for the same token) or buy_crypto_price, so the selection boundary 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