Skip to main content
Glama
aadarshvelu

Derive MCP Server

by aadarshvelu

get_all_instruments

Retrieve available financial instruments like options, perpetuals, or ERC20 tokens from Derive.xyz market data, with filters for type, currency, and expiration status.

Instructions

Get all available instruments (options, perps, or ERC20 tokens)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
expiredYesIf true, include expired instruments
instrument_typeYesInstrument type
currencyNoFilter by currency, e.g. ETH, BTC
pageNoPage number (default 1)
page_sizeNoResults per page (default 100, max 1000)

Implementation Reference

  • The handler function that executes the 'get_all_instruments' tool by making a POST request to the API.
    getAllInstruments(params: GetAllInstrumentsParams): Promise<unknown> {
      return this.post('public/get_all_instruments', params);
    }
  • src/tools.ts:39-51 (registration)
    Registration of the 'get_all_instruments' tool with its schema definition in src/tools.ts.
      name: 'get_all_instruments',
      description: 'Get all available instruments (options, perps, or ERC20 tokens)',
      inputSchema: {
        type: 'object',
        properties: {
          expired: { type: 'boolean', description: 'If true, include expired instruments' },
          instrument_type: { type: 'string', enum: INSTRUMENT_TYPE_ENUM, description: 'Instrument type' },
          currency: { type: 'string', description: 'Filter by currency, e.g. ETH, BTC' },
          ...paginationParams,
        },
        required: ['expired', 'instrument_type'],
      },
    },
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden but only states the basic read operation. Fails to mention pagination behavior, rate limits, authentication requirements, or what 'available' implies regarding instrument status.

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

Conciseness5/5

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

Single sentence of 9 words with action-fronted structure. No redundancy or waste, though brevity comes at the cost of behavioral details.

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?

Inadequate for a paginated listing tool with 5 parameters and no output schema. Description omits any mention of the paginated return structure, required filtering logic, or how the `expired` parameter affects results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Maps schema enum values (erc20, option, perp) to domain terminology (ERC20 tokens, options, perps), adding semantic context. However, it omits explanation of the `expired` flag's purpose and pagination strategy despite 100% schema coverage.

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 clear verb (Get) and resource (instruments) with specific scope clarification (options, perps, or ERC20 tokens). Distinguishes from singular `get_instrument` by specifying 'all', but lacks explicit cross-reference to guide selection between the two.

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 explicit guidance on when to use this versus siblings like `get_instrument` or `get_all_currencies`. No mention of when to apply the optional currency filter or pagination parameters.

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