Skip to main content
Glama

SouthPow crypto & market data

buy_coin_OXT

Paid. OXT/USD live: last price, 24h open/high/low, % change, 24h and 30d volume (Coinbase Exchange, Kraken cross-check). $0.10 USDC on Base. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/OXT.

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

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 supplied, the description carries the full burden well: it discloses the paid cost ($0.10 USDC on Base), payment rail, that no account or API key is needed, that failed calls are not charged, and that data comes from Coinbase Exchange with a Kraken cross-check. It stops short of describing response format or rate limits.

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 with 'Paid.' and the data payload, then cost, access terms, and endpoint URL, with no wasted sentences. The telegraphic style is dense but readable and every sentence adds information.

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?

With no annotations and no output schema, the description adequately covers cost, access requirements, data fields, and upstream sources. The main residual gap is the response shape/structure, which the absent output schema forces the agent to discover at call time.

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?

There are zero parameters, so the schema imposes nothing to explain; baseline is 4. The description correctly implies the ticker and dataset are fixed, requiring no input from the caller.

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?

States a specific subject and verb: 'OXT/USD live' with an explicit payload list (last price, 24h open/high/low, % change, 24h and 30d volume) and named sources. The ticker in the tool name plus this text lets an agent distinguish it from the ~300 sibling buy_coin_* tools, though the 'buy' verb in the name is misleading since this is a paid data read, not a purchase.

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 only implied: an agent can infer it should call this to fetch a live OXT/USD quote. There is no explicit when-to-use vs alternatives guidance (e.g. buy_crypto_price or other buy_coin_* siblings) and no statement of when not to call it.

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