Skip to main content
Glama
CohenD

fin-data-mcp-server

by CohenD

Crypto index candlesticks (OKX)

crypto_index_candles
Read-onlyIdempotent

Get OHLC candlestick data for OKX crypto indices (e.g., BTC-USD, ETH-USD) with configurable bar intervals and row limits.

Instructions

OHLC candlesticks for an OKX index (not a tradable instrument). Use index ids of the form 'BTC-USD' or 'ETH-USD'. Rows: [ts, open, high, low, close, confirm]. Example: { instId: "BTC-USD", bar: "1H", limit: 100 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barNo1H
limitNo
instIdYesIndex id, e.g. BTC-USD or ETH-USD
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds that it's for index only and specifies row format, adding useful context beyond annotations.

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 plus an example, front-loading key information. No wasted words.

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?

Describes row format, input parameters, and provides examples. Lacks explanation of 'confirm' field, but overall sufficient for a simple candlestick tool without output schema.

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?

Schema coverage is low (33% for instId only). Description compensates with examples and clarifies bar and limit usage via the example, but does not fully describe all parameters.

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?

Description clearly states it provides OHLC candlesticks for an OKX index, not a tradable instrument. Distinguishes from sibling 'crypto_candles' and gives example usage with 'instId'.

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?

Explicitly instructs to use index ids like 'BTC-USD' and contrasts with tradable instruments, but does not explicitly mention when not to use or list alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CohenD/fin-data-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server