Skip to main content
Glama
aadarshvelu

Derive MCP Server

by aadarshvelu
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

get_statistics

Retrieve aggregate platform statistics including volume and open interest for specified instruments from Derive.xyz market data.

Instructions

Get aggregate platform statistics (volume, open interest, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instrument_nameYesInstrument name or 'ALL', 'OPTION', 'PERP', 'SPOT'
currencyNoCurrency filter
end_timeNoEnd time in milliseconds

Implementation Reference

  • src/client.ts:157-159 (handler)
    The handler method in the DeriveClient class that performs the API request for 'get_statistics'.
    getStatistics(params: GetStatisticsParams): Promise<unknown> {
  return this.post('public/statistics', params);
}
  • src/tools.ts:214-225 (registration)
    Registration and schema definition for the 'get_statistics' MCP tool.
      name: 'get_statistics',
  description: 'Get aggregate platform statistics (volume, open interest, etc.)',
  inputSchema: {
    type: 'object',
    properties: {
      instrument_name: { type: 'string', description: "Instrument name or 'ALL', 'OPTION', 'PERP', 'SPOT'" },
      currency: { type: 'string', description: 'Currency filter' },
      end_time: { type: 'integer', description: 'End time in milliseconds' },
    },
    required: ['instrument_name'],
  },
},

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. Only behavioral disclosure is 'aggregate' implying summed data. Missing: time range behavior (if end_time omitted), whether data is real-time or cached, rate limits, and return structure.

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 sentence, front-loaded with no filler. Slightly weakened by 'etc.' vagueness, but otherwise tight and purposeful.

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?

Adequate for a simple 3-parameter read operation with complete schema documentation, but lacks critical context for an agent selecting between this and similar statistic-fetching siblings (get_ticker, get_tickers). No output schema exists, but that's acceptable for a standard data retrieval 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 coverage is 100%, so descriptions are complete in structured fields. The tool description adds semantic context that statistics include 'volume, open interest' (financial metrics) rather than restating parameter names, meeting the baseline expectation when schema is complete.

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 verb ('Get') and resource ('aggregate platform statistics') with concrete examples ('volume, open interest'). Could better distinguish from sibling 'get_ticker' which also retrieves statistics, but the 'aggregate' qualifier helps differentiate.

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 versus get_ticker or get_tickers, no mention of what happens when optional parameters (currency, end_time) are omitted, and no time-range guidance despite having an end_time parameter.

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