Skip to main content
Glama
aadarshvelu

Derive MCP Server

by aadarshvelu
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

get_ticker

Retrieve current market data including price, volume, and bid/ask quotes for financial instruments to monitor real-time trading conditions.

Instructions

Get current price, volume, bid/ask for an instrument

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instrument_nameYesInstrument name, e.g. ETH-PERP

Implementation Reference

  • src/client.ts:117-119 (handler)
    The `getTicker` method in the client class sends a POST request to the 'public/get_ticker' endpoint.
    getTicker(params: GetTickerParams): Promise<unknown> {
  return this.post('public/get_ticker', params);
}
  • src/types.ts:22-24 (schema)
    Definition of the parameters required for the get_ticker tool.
    export interface GetTickerParams {
  instrument_name: string;
}
  • src/index.ts:59-60 (registration)
    Registration/handling of the get_ticker tool call in the main entry point.
    case 'get_ticker':
  result = await client.getTicker(a as unknown as GetTickerParams);

Tool Definition Quality

B3.2/5.0
Behavior3/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 discloses that data is 'current' (implying real-time/snapshot) and specifies return fields (bid/ask), but omits caching behavior, rate limits, market hours constraints, or error handling for invalid instruments.

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, eight words, front-loaded action verb. Efficient but overly terse given the lack of annotations and output schema; sacrifices necessary behavioral context for brevity.

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 lookup tool but incomplete given the financial domain complexity and absence of output schema. Missing critical distinctions from similar sibling tools and operational details (data freshness, market status requirements).

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?

Input schema has 100% coverage with a clear example (ETH-PERP), establishing baseline 3. The description adds only 'for an instrument' which is redundant with the parameter name, providing no additional semantic context about instrument identifiers or formats.

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 data points retrieved (price, volume, bid/ask) using a clear action verb. However, it fails to differentiate from sibling 'get_tickers' (plural) which likely supports batch retrieval, or 'get_instrument' which may return static metadata.

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 single-instrument lookup versus the 'get_tickers' batch endpoint, or versus 'get_instrument'. No prerequisites or error conditions mentioned.

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