Skip to main content
Glama

Enflasyon etkisi

enflasyon_etkisi_hesapla
Read-onlyIdempotent

Bir tutarın verilen yıllık enflasyonla birkaç yıl sonraki alım gücü kaybını ve aynı alım için gereken tutarı hesaplar.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tutar": "<tutar>",
      "yillikEnflasyon": "<yillikEnflasyon>",
      "yil": "<yil>"
    },
    "name": "enflasyon_etkisi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
yilYesKaç yıl sonrası.
tutarYesBugünkü tutar (TL).
yillikEnflasyonYesBeklenen yıllık enflasyon (%).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds that two quantities are produced (loss and required amount), but does not disclose whether inflation is compounded annually or applied simply, nor anything about the return shape; with no output schema, that omission matters.

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?

A single, front-loaded sentence with no filler; the outcome (loss and required amount) is stated immediately. It is dense but every clause earns its place.

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?

For a simple three-parameter calculator with full schema coverage and safety annotations, the description is close to sufficient. The meaningful gap is the unstated compounding assumption and the absence of any return-value detail, which the missing output schema leaves entirely to the description.

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% and all three parameters carry their own descriptions (amount in TL, annual inflation in %, number of years), so the schema does the heavy lifting. The description adds no meaning beyond that, which is the baseline 3 case.

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?

Specific verb and resource: it states it computes the purchasing-power loss of an amount after several years at a given annual inflation rate, plus the amount needed to preserve the same purchasing power. That distinguishes it from rate-retrieval siblings, though it never names enflasyon_orani_getir or paranin_bugunku_degeri_hesapla explicitly.

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 gives no when-to-use or when-not guidance and does not point at alternatives, such as fetching the rate first via enflasyon_orani_getir or using the present-value tool for the reverse direction. At best the calculation scenario implies its purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources