Skip to main content
Glama
aadarshvelu

Derive MCP Server

by aadarshvelu
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

get_spot_feed_history_candles

Retrieve historical OHLC candlestick data for cryptocurrency spot prices to analyze market trends and price movements over specified time periods.

Instructions

Get OHLC candlestick data for spot prices

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyYesCurrency, e.g. ETH, BTC
start_timestampYesStart timestamp in seconds
end_timestampYesEnd timestamp in seconds
periodYesCandle period in seconds: 60, 300, 900, 1800, 3600, 14400, 28800, 86400, or 604800

Implementation Reference

  • src/client.ts:129-131 (handler)
    The actual implementation of the tool, defined as a method on the DeriveClient class which makes a POST request to the API.
    getSpotFeedHistoryCandles(params: GetSpotFeedHistoryCandlesParams): Promise<unknown> {
  return this.post('public/get_spot_feed_history_candles', params);
}
  • src/index.ts:68-69 (handler)
    The MCP request handler that routes the tool name to the appropriate client method.
    case 'get_spot_feed_history_candles':
  result = await client.getSpotFeedHistoryCandles(a as unknown as GetSpotFeedHistoryCandlesParams);
  • src/tools.ts:102-104 (registration)
    The MCP tool definition (schema and registration) for 'get_spot_feed_history_candles'.
    name: 'get_spot_feed_history_candles',
description: 'Get OHLC candlestick data for spot prices',
inputSchema: {

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. While 'Get' implies read-only, there is no disclosure about pagination behavior, maximum date range limits, rate limiting, or whether data is real-time vs historical. Critical gaps for a financial data API.

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?

Extremely brief at 7 words. No filler content, but arguably under-specified rather than optimally concise given the lack of annotations and output schema. Front-loads the essentials without wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Mentions 'OHLC' which hints at return structure (compensating somewhat for missing output schema). The complete input schema helps, but for a 4-parameter financial tool with no annotations, the description lacks critical context about data behavior and constraints.

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?

Input schema has 100% coverage with detailed descriptions (including specific period values like 60, 300, etc.). The description adds no parameter-specific context, but baseline 3 is appropriate since schema does the heavy lifting.

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 specific action ('Get') and resource ('OHLC candlestick data'), and identifies the domain ('spot prices'). However, it fails to distinguish from sibling tool 'get_spot_feed_history' which likely returns non-aggregated data.

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

Usage Guidelines2/5

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

Provides no guidance on when to use this tool versus the sibling 'get_spot_feed_history' or other historical data tools. No mention of appropriate time ranges or use cases for candlestick vs raw data.

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/aadarshvelu/derive-mcp'

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