Skip to main content
Glama

SouthPow crypto & market data

buy_tok_KORUB

Paid. South Korea Bull 3X ETF (bStocks Tokenized ETF) (KORUB) 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/KORUB.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it declares the tool is paid, prices it ($0.05 USDC), lists accepted payment chains (Base or Solana), states no account or API key is needed, and that failed calls are not charged. It omits rate limits, latency, and whether the price is cached or real-time across venues, so it stops short of 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?

'Paid.' is front-loaded so the agent learns cost before anything else, then payload, then payment mechanics, then endpoint URL. The middle sentence is dense with semicolon-less clauses but each piece of information is load-bearing; nothing is redundant.

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, no-annotation tool with no output schema, the description still enumerates the returned fields (price, 24h change, market-cap rank) and covers cost, auth, failure behavior, and endpoint. The main missing piece is any indication of data freshness or response envelope shape, which is minor given the tool's simplicity.

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; the baseline of 4 applies. The token identity is fixed in the tool name and reiterated as KORUB in the description, which is the only relevant 'parameter-like' semantic.

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 (South Korea Bull 3X ETF, KORUB) and the exact payload returned: live USD price, 24h change, and market-cap rank. That makes it clearly a price-fetch tool rather than a purchase action, despite the 'buy_' name prefix. It does not explicitly contrast itself with the hundreds of buy_tok_* siblings or with buy_crypto_price, so it falls short of a 5.

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 ticker-specific payload, but there is no explicit statement of when to pick this over buy_crypto_price or another token endpoint, and no exclusions. The only guidance given is operational ('No account, no API key'), not selection guidance.

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