Skip to main content
Glama
kemalersin

FonParam MCP

by kemalersin

monthly_inflation_rate

Retrieve inflation data for a specific month and year to analyze economic trends and inform financial decisions.

Instructions

Belirli bir ay ve yıldaki enflasyon verisini getirir

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
yearYesYıl
monthYesAy (1-12)

Implementation Reference

  • Handler for the 'monthly_inflation_rate' tool that calls the API client to get inflation rate for specified year and month.
    case 'monthly_inflation_rate':
      return await this.apiClient.getInflationRateByMonth(args.year, args.month);
  • src/tools.ts:450-470 (registration)
    Registration of the 'monthly_inflation_rate' tool in the getTools() method, defining name, description, and input schema.
    {
      name: 'monthly_inflation_rate',
      description: 'Belirli bir ay ve yıldaki enflasyon verisini getirir',
      inputSchema: {
        type: 'object',
        properties: {
          year: {
            type: 'number',
            description: 'Yıl',
            minimum: 2000
          },
          month: {
            type: 'number',
            description: 'Ay (1-12)',
            minimum: 1,
            maximum: 12
          }
        },
        required: ['year', 'month']
      }
    }
  • Input schema for the 'monthly_inflation_rate' tool, specifying year (number >=2000) and month (1-12) as required parameters.
    inputSchema: {
      type: 'object',
      properties: {
        year: {
          type: 'number',
          description: 'Yıl',
          minimum: 2000
        },
        month: {
          type: 'number',
          description: 'Ay (1-12)',
          minimum: 1,
          maximum: 12
        }
      },
      required: ['year', 'month']
    }
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 fetches data (implying a read-only operation) but doesn't describe what 'enflasyon verisini' includes (e.g., rate value, source, format), error handling, rate limits, or authentication needs. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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

Conciseness5/5

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

The description is a single, efficient sentence in Turkish that directly states the tool's function without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence contributes to understanding the purpose.

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 tool's moderate complexity (fetching specific data), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what the inflation data includes (e.g., numerical rate, metadata), potential errors, or how results are structured. For a data retrieval tool with no structured output information, more context is needed to guide effective use.

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?

The description mentions 'Belirli bir ay ve yıldaki' (a specific month and year), which aligns with the two parameters in the schema. Since schema description coverage is 100% (with descriptions for 'year' and 'month'), the description adds minimal value beyond what the schema provides. It doesn't explain parameter interactions or provide additional context, so it meets the baseline for high schema coverage.

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 clearly states the tool's purpose: 'getirir' (fetches/retrieves) 'enflasyon verisini' (inflation data) for 'Belirli bir ay ve yıldaki' (a specific month and year). It specifies the verb (fetch) and resource (inflation data) with temporal scope. However, it doesn't explicitly differentiate from sibling tools like 'inflation_rates' or 'latest_inflation_rate', which prevents a perfect score.

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. It doesn't mention sibling tools like 'inflation_rates' (which might provide multiple rates) or 'latest_inflation_rate' (which might get the most recent data), nor does it specify prerequisites or exclusions. Usage is implied by the temporal parameters but not explicitly 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