Skip to main content
Glama
aadarshvelu

Derive MCP Server

by aadarshvelu

get_latest_signed_feeds

Retrieve current oracle price feeds for currencies and instruments from Derive.xyz market data. Filter by currency or expiry to access real-time financial information.

Instructions

Get current oracle price feeds

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
currencyNoCurrency filter (defaults to all)
expiryNoExpiry filter (0 for spot/perp only, defaults to all)

Implementation Reference

  • The handler implementation for 'get_latest_signed_feeds' which calls the API.
    getLatestSignedFeeds(params: GetLatestSignedFeedsParams): Promise<unknown> {
      return this.post('public/get_latest_signed_feeds', params);
    }
  • The type definition for 'GetLatestSignedFeedsParams'.
    export interface GetLatestSignedFeedsParams {
      currency?: string;
      expiry?: number;
  • src/tools.ts:153-163 (registration)
    Tool registration definition for 'get_latest_signed_feeds'.
    {
      name: 'get_latest_signed_feeds',
      description: 'Get current oracle price feeds',
      inputSchema: {
        type: 'object',
        properties: {
          currency: { type: 'string', description: 'Currency filter (defaults to all)' },
          expiry: { type: 'integer', description: 'Expiry filter (0 for spot/perp only, defaults to all)' },
        },
      },
    },
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. It mentions 'oracle' indicating data source, but omits critical behavioral details: what 'signed' entails (cryptographic signatures?), data freshness guarantees, verification requirements, or return format.

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 of four words with no redundancy. Front-loaded and efficient, though undersized for the domain complexity rather than unnecessarily verbose.

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?

For a financial oracle tool with signed data (implying cryptographic complexity), the description is insufficient. No output schema is present, yet the description doesn't hint at return structure, signature format, or validation needs.

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%, documenting both the currency and expiry filters. The description adds no parameter-specific guidance, meeting the baseline for well-documented schemas.

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 it retrieves oracle price feeds with a specific verb and resource, but fails to explain what 'signed' means (present in the tool name) or differentiate from sibling price tools like get_spot_feed_history or get_ticker.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 alternatives. Siblings include multiple price-related endpoints (get_ticker, get_spot_feed_history), but no selection criteria or prerequisites are offered.

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