Skip to main content
Glama
aadarshvelu

Derive MCP Server

by aadarshvelu
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

get_option_settlement_history

Retrieve historical option settlement data from Derive to analyze past market outcomes and settlement prices for informed trading decisions.

Instructions

Get historical option settlement data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
page_sizeNoResults per page (default 100, max 1000)
subaccount_idNoFilter by subaccount ID

Implementation Reference

  • src/client.ts:141-143 (handler)
    The implementation of the getOptionSettlementHistory client method which performs the API call.
    getOptionSettlementHistory(params: GetOptionSettlementHistoryParams): Promise<unknown> {
  return this.post('public/get_option_settlement_history', params);
}
  • src/index.ts:77-79 (registration)
    The registration of the get_option_settlement_history tool in the main request handler.
    case 'get_option_settlement_history':
  result = await client.getOptionSettlementHistory(a as unknown as GetOptionSettlementHistoryParams);
  break;
  • src/types.ts:60-64 (schema)
    Type definition for the parameters of the get_option_settlement_history tool.
    export interface GetOptionSettlementHistoryParams {
  page?: number;
  page_size?: number;
  subaccount_id?: number;
}
  • src/tools.ts:143-148 (schema)
    MCP tool definition for get_option_settlement_history.
    name: 'get_option_settlement_history',
description: 'Get historical option settlement data',
inputSchema: {
  type: 'object',
  properties: {
    ...paginationParams,

Tool Definition Quality

C2.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers almost none. It does not confirm the read-only/safe nature of the operation, describe pagination behavior, time range limitations, or what data fields are returned in the settlement records.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The four-word description contains no fluff or redundancy, but is arguably underspecified given the lack of annotations and output schema. It is front-loaded (purpose first) but too minimal to fully earn its place as the sole documentation source.

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?

Given zero annotations, no output schema, and three parameters controlling pagination and filtering, the description fails to provide necessary behavioral context. It should explain the settlement domain, pagination limits, and safety profile, but offers only the tool name restated as a sentence.

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 description coverage is 100%, with clear descriptions for page, page_size, and subaccount_id. The description adds no additional parameter context, meeting the baseline expectation when the schema does the documentation work. No compensation needed for missing schema docs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the basic verb ('Get') and resource ('historical option settlement data'), but provides minimal specificity about what 'settlement' encompasses (expiries? exercises?) and does not differentiate from sibling history tools like get_funding_rate_history or get_liquidation_history despite the crowded tool namespace.

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 provided on when to use this versus other history endpoints, when pagination is required, or prerequisites like subaccount requirements. The description is purely declarative with no contextual usage hints.

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