Skip to main content
Glama

KDV

kdv_hesapla
Read-onlyIdempotent

KDV ekler ya da KDV dahil tutardan ayırır. Oranlar: %1, %10, %20.

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>"
    },
    "name": "kdv_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
yonNokdv-ayir: tutar KDV dahil. Varsayılan kdv-ekle.
oranNo%. Varsayılan 20.
tutarYesTutar (TL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / oran / description
      Previous value: -"KDV oranı (%). Varsayılan 20."New value: +"%. Varsayılan 20."
    • changedInput schema / properties / yon / description
      Previous value: -"kdv-ekle: tutar KDV hariçtir; kdv-ayir: tutar KDV dahildir. Varsayılan kdv-ekle."New value: +"kdv-ayir: tutar KDV dahil. Varsayılan kdv-ekle."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine domain behavior beyond that: the two operating modes and the fact that the valid rate set is limited to 1%, 10%, and 20% — information the schema's unconstrained `number, minimum 0` does not convey.

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?

Two short sentences, both front-loaded with the highest-value facts (what it does, then the valid rates). No filler, no repetition of the title or parameter names.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter, fully-documented, fully-annotated single-purpose calculator, the description supplies the one thing structured data lacks: the valid rate domain. No output schema exists, but the return value of a KDV computation is self-evident enough that its absence is not a real gap.

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?

Schema coverage is 100%, so the baseline would be 3, but the description earns a bump by constraining `oran` to the three real Turkish VAT rates (1/10/20), which the schema permits any non-negative number for. It still adds nothing about how `tutar` and `yon` interact beyond what the schema already documents.

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 names the specific operation and both directions it supports: adding VAT ("KDV ekler") or extracting it from a VAT-inclusive amount ("KDV dahil tutardan ayırır"). This is clearly a VAT calculator and is readily distinguishable from siblings like kira_artis_hesapla or kredi_hesapla, though it never explicitly says so.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the domain — the text never states when to pick this tool versus a sibling, nor when to choose the add versus subtract direction. The direction semantics actually live in the schema's `yon` description, not in the tool description, so guidance here is minimal-but-adequate.

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