Skip to main content
Glama
Sign In

Okx

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Market 24hr

market_24hr
Read-onlyIdempotent

OKX crypto exchange 24-hour rolling stats for an instrument: open, high, low, last, volume, vol-ccy. Use for daily summary on OKX.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "instId": "BTC-USDT"
    },
    "name": "market_24hr"
  }
}

Input Schema

NameRequiredDescriptionDefault
instIdYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds the list of returned fields but does not disclose any additional behavioral traits (e.g., timezone, data freshness, or exact rolling window definition).

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?

Two concise sentences that front-load the tool's purpose and provide a practical use case. No unnecessary filler or repetition.

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 simple one-parameter tool with an output schema and comprehensive annotations, the description covers purpose, usage, and data fields. The only minor gap is ambiguity about what 'rolling' means (e.g., exact time boundary), but this is acceptable for the tool's simplicity.

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?

The schema provides zero description for instId, so the description must compensate. 'for an instrument' hints that instId is an instrument identifier, but it doesn't specify the format or give examples. The schema's example 'BTC-USDT' covers some of this gap, but the description could be more explicit about what to pass.

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?

Clearly states it retrieves OKX 24-hour rolling stats for an instrument and enumerates the exact fields (open, high, low, last, volume, vol-ccy). It differentiates from sibling tools like 'ticker' or 'candles' by focusing on a rolling 24-hour aggregate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit use case: 'Use for daily summary on OKX.' This gives context for when to select this tool. However, it does not mention alternative tools or exclusions, so it's not a full when/when-not statement.

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

All Okx toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources