Skip to main content
Glama
aadarshvelu

Derive MCP Server

by aadarshvelu

get_funding_rate_history

Retrieve historical funding rates for perpetual instruments to analyze market trends and funding costs over time.

Instructions

Get historical funding rates for a perpetual instrument

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instrument_nameYesPerp instrument name, e.g. ETH-PERP
start_timestampNoStart timestamp in seconds (default 0, max 30 days ago)
end_timestampNoEnd timestamp in seconds (default now)
periodNoPeriod in seconds

Implementation Reference

  • The implementation of the get_funding_rate_history tool, which makes a POST request to the Derive API.
    getFundingRateHistory(params: GetFundingRateHistoryParams): Promise<unknown> {
      return this.post('public/get_funding_rate_history', params);
    }
  • src/index.ts:71-73 (registration)
    Registration and routing of the get_funding_rate_history tool call in the main MCP server request handler.
    case 'get_funding_rate_history':
      result = await client.getFundingRateHistory(a as unknown as GetFundingRateHistoryParams);
      break;
  • Type definition for the parameters of the get_funding_rate_history tool.
    export interface GetFundingRateHistoryParams {
      instrument_name: string;
      start_timestamp?: number;
Behavior2/5

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

Zero annotations provided, so description carries full disclosure burden. Fails to mention read-only nature, pagination behavior, rate limiting, or that data is limited to 30 days (constraint buried in schema but not described). Doesn't explain what funding rates represent (periodic payments between long/short positions).

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?

Single 7-word sentence with zero redundancy. Front-loaded with action verb. However, extreme brevity leaves it under-specified; conciseness becomes under-conciseness given the tool's complexity and lack of supporting annotations.

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

Completeness2/5

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

Financial data tool with 4 parameters including time ranges, yet no output schema provided. Description fails to indicate return format (array of rate objects?), data granularity, or that funding rates are typically 8-hour or 1-hour intervals. Missing crucial context for a derivative/finance API tool.

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 has 100% description coverage (all 4 params documented). Description adds 'perpetual instrument' context for instrument_name but provides no additional semantics for timestamp formats, period granularity selection guidance, or default value behaviors beyond what's in the schema. Baseline 3 appropriate given schema completeness.

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?

Clear verb 'Get' with specific resource 'historical funding rates' and scope 'perpetual instrument'. Distinguishes from generic 'history' tools and correctly identifies the domain (perpetual swaps vs spot/options). However, doesn't explicitly differentiate from sibling get_interest_rate_history despite both being rate histories.

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?

No guidance on when to use this tool versus siblings like get_spot_feed_history or get_interest_rate_history. No mention of prerequisites (e.g., needing a valid instrument_name from get_instruments) or typical use cases (calculating funding costs over time).

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