Skip to main content
Glama

SouthPow crypto & market data

buy_tok_OSAK

Paid. Osaka Protocol (OSAK) price: live USD price, 24h change and market-cap rank. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/OSAK.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 declares the tool is paid, the exact price ($0.05 USDC on Base or Solana), that failed calls are not charged, and that no account/API key is required. It omits how payment is actually transacted and any rate limits or latency expectations.

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-loads the most decision-relevant fact ("Paid") before the resource and payload, then compresses cost, auth, billing behavior, and endpoint into short clauses. No sentence is filler, and the fixed price is stated numerically rather than vaguely.

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 paid lookup with no output schema, the description supplies the return fields, the cost, the accepted chains, and the failure-billing policy — enough to decide and call. The one real gap is that it never explains the payment handshake an agent must complete before a paid call succeeds.

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 meaning for the description to add; the baseline for a parameterless tool applies. The asset is baked into the tool rather than passed in, which the description implicitly confirms by never referencing any input.

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 a specific verb+resource ("Osaka Protocol (OSAK) price") and enumerates the returned fields: live USD price, 24h change, market-cap rank. The tool name already fixes the asset, so there is no ambiguity against siblings like buy_crypto_price or buy_coin_*.

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?

The description makes clear this is a paid, single-asset price lookup with no account or key needed, so an agent can infer when it applies. It never states when to prefer a sibling (e.g. buy_crypto_price for multi-asset quotes) or when to skip the paid call, leaving routing 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