Skip to main content
Glama
kemalersin

FonParam MCP

by kemalersin

fund_historical_data

Retrieve historical fund performance data for analysis by specifying fund code, date range, and interval to track investment trends.

Instructions

Fonun geçmiş değerlerini getirir

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesFon kodu
start_dateNoBaşlangıç tarihi (YYYY-MM-DD)
end_dateNoBitiş tarihi (YYYY-MM-DD)
intervalNoVeri aralığı
sortNoSıralama alanı
orderNoSıralama yönü

Implementation Reference

  • Executes the core tool logic by making an HTTP GET request to the API endpoint `/funds/{code}/historical` to retrieve the fund's historical data values.
    async getFundHistoricalData(code: string, params: HistoricalDataParams = {}): Promise<FundHistoricalValue[]> {
      const response: AxiosResponse<FundHistoricalValue[]> = await this.client.get(`/funds/${code}/historical`, { params });
      return response.data;
    }
  • src/tools.ts:226-261 (registration)
    Registers the 'fund_historical_data' tool in the MCP tools list with description and input schema definition.
    {
      name: 'fund_historical_data',
      description: 'Fonun geçmiş değerlerini getirir',
      inputSchema: {
        type: 'object',
        properties: {
          code: {
            type: 'string',
            description: 'Fon kodu'
          },
          start_date: {
            type: 'string',
            description: 'Başlangıç tarihi (YYYY-MM-DD)'
          },
          end_date: {
            type: 'string',
            description: 'Bitiş tarihi (YYYY-MM-DD)'
          },
          interval: {
            type: 'string',
            description: 'Veri aralığı',
            enum: ['daily', 'weekly', 'monthly']
          },
          sort: {
            type: 'string',
            description: 'Sıralama alanı'
          },
          order: {
            type: 'string',
            description: 'Sıralama yönü',
            enum: ['ASC', 'DESC']
          }
        },
        required: ['code']
      }
    },
  • Zod schema used for input validation and parsing of the 'fund_historical_data' tool arguments.
    const HistoricalDataSchema = z.object({
      code: z.string(),
      start_date: z.string().optional(),
      end_date: z.string().optional(),
      interval: z.enum(['daily', 'weekly', 'monthly']).optional(),
      sort: z.string().optional(),
      order: z.enum(['ASC', 'DESC']).optional()
    });
  • TypeScript interface defining the parameters for historical data requests, used in the API client.
    export interface HistoricalDataParams {
      start_date?: string;
      end_date?: string;
      interval?: 'daily' | 'weekly' | 'monthly';
      sort?: string;
      order?: 'ASC' | 'DESC';
    }
  • Dispatches the tool call in handleToolCall by parsing inputs and invoking the API client's getFundHistoricalData method.
    case 'fund_historical_data':
      const historicalParams = HistoricalDataSchema.parse(args);
      const { code, ...histParams } = historicalParams;
      return await this.apiClient.getFundHistoricalData(code, histParams);
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 only states it 'gets' historical values, implying a read-only operation, but doesn't cover critical aspects like authentication needs, rate limits, error handling, or what the return format looks like (e.g., structured data, pagination). This leaves significant gaps for a tool with 6 parameters and no output schema.

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 a single, efficient sentence in Turkish, front-loading the core purpose without unnecessary words. However, it's overly brief for a tool with 6 parameters and no annotations, potentially under-specifying rather than being optimally concise. It earns a 4 for zero waste but could benefit from slightly more detail given the context.

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?

Given the complexity (6 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return values, error cases, or behavioral traits like data freshness or limitations. Siblings like 'analyze_fund' suggest this might be part of a financial analysis suite, but no integration context is provided. The description is inadequate for safe and effective use by an AI agent.

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 parameters (e.g., 'code' as fund code, dates in YYYY-MM-DD, enums for interval and order). The description adds no additional meaning beyond the schema, such as explaining parameter interactions or default behaviors. Baseline 3 is appropriate since the schema does the heavy lifting, but no extra value is added.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Fonun geçmiş değerlerini getirir' (Get historical values of the fund) states a basic purpose but is vague. It specifies the resource ('fon' - fund) and a general action ('getirir' - get), but lacks specificity about what historical values (e.g., prices, returns) and doesn't distinguish from siblings like 'analyze_fund' or 'compare_funds'. It's not tautological but remains too broad for clear differentiation.

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 guidance on when to use this tool versus alternatives is provided. The description implies it retrieves historical data, but there's no mention of prerequisites, exclusions, or comparisons to siblings like 'statistics_by_date' or 'top_performing_funds'. Usage is implied by the name and description alone, with no explicit context or alternatives stated.

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/kemalersin/fonparam-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server