Derive MCP Server

get_liquidation_history

Retrieve historical liquidation events from Derive.xyz to analyze market risk and trading patterns using timestamp-based queries.

Instructions

Get historical liquidation events

Input Schema

TableJSON Schema

Name	Required	Description
`start_timestamp`	No	Start timestamp in seconds (default 0)
`end_timestamp`	No	End timestamp in seconds (default now)
`page`	No	Page number (default 1)
`page_size`	No	Results per page (default 100, max 1000)

Implementation Reference

src/client.ts:149-151 (handler)
The `getLiquidationHistory` method in the `DeriveClient` class implements the tool logic by making a POST request to the `public/get_liquidation_history` API endpoint.
```
getLiquidationHistory(params: GetLiquidationHistoryParams): Promise<unknown> {
  return this.post('public/get_liquidation_history', params);
}
```

src/tools.ts:165-175 (registration)

The tool `get_liquidation_history` is defined and registered in `src/tools.ts`, including its input schema description and properties.

  name: 'get_liquidation_history',
  description: 'Get historical liquidation events',
  inputSchema: {
    type: 'object',
    properties: {
      start_timestamp: { type: 'integer', description: 'Start timestamp in seconds (default 0)' },
      end_timestamp: { type: 'integer', description: 'End timestamp in seconds (default now)' },
      ...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 disclosure burden but reveals only that the data is 'historical'. It omits safety confirmation (read-only nature), pagination behavior implications (despite page parameters existing), data volume expectations, or authentication requirements.

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?

While the four-word description is extremely concise and front-loaded, it is underspecified rather than appropriately minimal. The brevity sacrifices necessary contextual detail for a data retrieval tool with temporal filtering and pagination.

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?

Complexity includes date ranges and pagination (4 parameters), yet the description provides no output format details, no explanation of pagination strategy, no data retention limits, and no domain context given the absence of both annotations and output schema.

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?

With 100% schema description coverage, the input schema already documents all four parameters (timestamps, pagination). The description adds no semantic context beyond the schema, but baseline 3 is appropriate given the schema completeness.

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 action (Get) and resource (historical liquidation events), but lacks specificity about what constitutes these events (e.g., forced position closures) and fails to differentiate from sibling history tools like get_funding_rate_history or get_option_settlement_history.

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 versus alternative data sources, no mention of data retention limits, rate limiting, or prerequisites for accessing liquidation history.

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

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

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