Skip to main content
Glama
aadarshvelu

Derive MCP Server

by aadarshvelu
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

get_interest_rate_history

Retrieve historical borrowing interest rate data for specified time periods to analyze market trends and inform financial decisions.

Instructions

Get historical borrowing interest rates

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_timestamp_secYesStart timestamp in seconds
to_timestamp_secYesEnd timestamp in seconds
pageNoPage number (default 1)
page_sizeNoResults per page (default 100, max 1000)

Implementation Reference

  • src/client.ts:137-139 (handler)
    The handler implementation for the tool 'get_interest_rate_history' in the client class, which dispatches a POST request.
    getInterestRateHistory(params: GetInterestRateHistoryParams): Promise<unknown> {
  return this.post('public/get_interest_rate_history', params);
}
  • src/tools.ts:130-141 (registration)
    Registration of the 'get_interest_rate_history' tool with its schema definition in src/tools.ts.
      name: 'get_interest_rate_history',
  description: 'Get historical borrowing interest rates',
  inputSchema: {
    type: 'object',
    properties: {
      from_timestamp_sec: { type: 'integer', description: 'Start timestamp in seconds' },
      to_timestamp_sec: { type: 'integer', description: 'End timestamp in seconds' },
      ...paginationParams,
    },
    required: ['from_timestamp_sec', 'to_timestamp_sec'],
  },
},

Tool Definition Quality

C2.9/5.0
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 of behavioral disclosure. It fails to indicate this is a read-only operation, omits pagination behavior details (despite having page/page_size parameters), and does not mention rate limits or data granularity.

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?

The description is extremely concise at only 4 words. While efficient and front-loaded with the verb, it is arguably under-specified given the lack of annotations and output schema. No wasted words, but misses opportunity to add value.

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?

Despite having 4 parameters (2 required) with full schema documentation, the description lacks necessary context for a data retrieval tool: no mention of result format, time range limits, or pagination requirements. Without an output schema or annotations, the description should compensate but does not.

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%, with clear descriptions for all 4 parameters including timestamp units and pagination constraints. The description adds no parameter semantics beyond the schema, which is acceptable given the complete schema coverage, warranting the baseline score.

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?

The description uses a specific verb ('Get') and resource ('historical borrowing interest rates'), making the purpose clear. It implicitly distinguishes from sibling 'get_funding_rate_history' by specifying 'borrowing' vs 'funding', though it could explicitly clarify this distinction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_funding_rate_history', nor does it mention prerequisites such as valid time ranges or maximum date spans.

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