Skip to main content
Glama
kemalersin

FonParam MCP

by kemalersin

latest_statistics

Retrieve current investment fund statistics from Turkey's FonParam API to analyze and compare fund performance data.

Instructions

Son istatistikleri getirir

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Core implementation of the tool logic: makes HTTP GET request to '/statistics/latest' endpoint and returns DailyStatistics.
    async getLatestStatistics(): Promise<DailyStatistics> {
      const response: AxiosResponse<DailyStatistics> = await this.client.get('/statistics/latest');
      return response.data;
    }
  • src/tools.ts:360-367 (registration)
    Registration of the 'latest_statistics' tool in getTools(), including description and empty input schema (no parameters required).
    {
      name: 'latest_statistics',
      description: 'Son istatistikleri getirir',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Tool dispatch handler in handleToolCall switch statement that delegates to the apiClient.getLatestStatistics() method.
    case 'latest_statistics':
      return await this.apiClient.getLatestStatistics();
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'gets' (retrieves) statistics, implying a read-only operation, but doesn't specify what format the statistics are returned in, whether there are rate limits, authentication requirements, or any side effects. The description is too vague to provide meaningful behavioral context beyond the basic action.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence ('Son istatistikleri getirir'), which is concise but under-specified rather than efficiently informative. It lacks front-loaded critical details (e.g., what statistics, for what purpose), making it feel incomplete rather than optimally structured. It earns its place minimally but doesn't excel in clarity or structure.

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 (implied by sibling tools in a financial domain) and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'latest statistics' means (e.g., time frame, data source, return format), leaving significant gaps for an AI agent to understand how to use this tool effectively in context with other tools like 'statistics' or 'statistics_by_date'.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage (empty schema), so no parameter documentation is needed. The description doesn't add parameter information, which is appropriate here. A baseline of 4 is given as the description doesn't need to compensate for any parameter gaps, though it could theoretically mention implicit parameters (like none required).

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 'Son istatistikleri getirir' (Turkish for 'Gets the latest statistics') is a tautology that essentially restates the tool name 'latest_statistics' in verb form. It doesn't specify what kind of statistics (financial, economic, fund-related) or from what domain, though the sibling tools suggest a financial context. The description fails to distinguish this tool from sibling tools like 'statistics' or 'statistics_by_date'.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'latest_statistics' over 'statistics' (which might provide broader or historical data) or 'statistics_by_date' (which likely allows date-specific queries), nor does it indicate any prerequisites or exclusions for usage.

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