Skip to main content
Glama
aadarshvelu

Derive MCP Server

by aadarshvelu

get_tickers

Retrieve ticker symbols for financial instruments by type, with filters for currency and expiry date to access market data.

Instructions

Get tickers for all instruments of a given type

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instrument_typeYesInstrument type
currencyNoCurrency filter (required for options)
expiry_dateNoExpiry date filter for options (YYYYMMDD format)

Implementation Reference

  • The `getTickers` method in `DeriveClient` sends a POST request to the 'public/get_tickers' endpoint.
    getTickers(params: GetTickersParams): Promise<unknown> {
      return this.post('public/get_tickers', params);
    }
  • src/tools.ts:75-86 (registration)
    The 'get_tickers' tool is defined in the tools list with its input schema.
      name: 'get_tickers',
      description: 'Get tickers for all instruments of a given type',
      inputSchema: {
        type: 'object',
        properties: {
          instrument_type: { type: 'string', enum: INSTRUMENT_TYPE_ENUM, description: 'Instrument type' },
          currency: { type: 'string', description: 'Currency filter (required for options)' },
          expiry_date: { type: 'string', description: 'Expiry date filter for options (YYYYMMDD format)' },
        },
        required: ['instrument_type'],
      },
    },
  • The request handler in `src/index.ts` calls `client.getTickers` when the 'get_tickers' tool is invoked.
    case 'get_tickers':
      result = await client.getTickers(a as unknown as GetTickersParams);
Behavior2/5

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

No annotations provided, so description carries full behavioral burden. Discloses nothing about read-only safety, rate limits, real-time vs cached data, or what specific data fields a 'ticker' contains beyond the basic retrieval action.

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 9-word sentence is appropriately front-loaded and waste-free. However, extreme brevity is insufficient given zero annotations and conditional parameter logic that requires explanation.

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?

With 100% schema coverage, parameter documentation is complete. However, lacks necessary context about option-specific filtering behavior and sibling differentiation that would prevent selection errors.

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 schema documents all parameters (instrument_type, currency, expiry_date) adequately. Description mentions 'type' (mapping to instrument_type) but adds no semantic detail about currency/expiry_date being option-specific filters. Baseline 3 appropriate given schema carries load.

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?

States specific action ('Get tickers') and resource scope ('all instruments of a given type'), but fails to distinguish from sibling tool 'get_ticker' (singular) or clarify when bulk retrieval is preferred over single-instrument queries.

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 tool versus 'get_ticker', 'get_all_instruments', or other siblings. Does not mention the conditional requirement that 'currency' is only required for options, despite this being critical usage context.

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