Skip to main content
Glama
OKX Market Guard

OKX Market Guard

by mavis-codee

Market ticker

market_ticker
Read-onlyIdempotent

Retrieve the current OKX public ticker for a specified spot or swap instrument without requiring API keys, orders, or account access.

Instructions

Get the latest OKX public ticker for one instrument (spot or swap). READ-ONLY: this tool only calls OKX public market REST. No API key, no order, no account access. Example instId: BTC-USDT or BTC-USDT-SWAP.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instId": "<instId>"
    },
    "name": "market_ticker"
  }
}

Input Schema

NameRequiredDescriptionDefault
instIdYesOKX instrument ID, e.g. BTC-USDT (spot) or BTC-USDT-SWAP (perpetual).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description goes further with auth details — 'No API key, no order, no account access' — which is genuinely useful context for an agent deciding whether credentials are needed, though rate limits and response shape go unmentioned.

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?

Three short sentences, front-loaded with the core action before the safety and example details. The READ-ONLY clause slightly overlaps the readOnlyHint annotation, but it is brief and not wasteful.

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 one-parameter read tool with rich annotations, the definition covers purpose, credential requirements, and input format. The main residual gap is that no output schema exists and the description never says what a ticker contains (last, bid/ask, volume), so return interpretation is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single instId parameter is fully documented in the schema, including spot and perpetual examples. The description's example values restate that rather than adding new syntax, so baseline 3 applies.

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?

Uses a specific verb and resource ('Get the latest OKX public ticker') scoped to one instrument and explicitly to spot or swap. It implicitly separates itself from history-oriented siblings via 'latest', but never names an alternative tool outright.

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?

Implies the use case (retrieve current price snapshot for a single instrument) and supplies example instId formats, but gives no explicit when-not guidance or pointer to a sibling such as market_candles for historical data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.