Türkiye Vergi MCP

by BrkAzmn

Overview Schema Source Related Servers Discussions Admin

Python

Stopaj hesapla

stopaj_hesapla

Read-only

Calculate withholding tax and optional VAT on gross or net amounts using a user-provided rate.

Instructions

Kullanici tarafindan verilen oranla brut/net stopaj ve opsiyonel KDV 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>",
      "stopaj_orani": "<stopaj_orani>"
    },
    "name": "stopaj_hesapla"
  }
}

Input Schema

Name	Required	Default
`tutar`	Yes
`kdv_orani`	No
`tutar_tipi`	No	brut
`stopaj_orani`	Yes

Output Schema

Name	Required	Default
`uyarilar`	No
`kaynaklar`	No
`net_tutar`	Yes
`brut_tutar`	Yes
`kdv_tutari`	Yes
`tutar_tipi`	Yes
`para_birimi`	No	TRY
`varsayimlar`	No
`yasal_uyari`	No	Bu cikti genel bilgilendirme amaclidir; hukuki veya mali musavirlik gorusu degildir. Isleme ozgu kosullar icin guncel resmi metni ve yetkili uzmani kontrol edin.
`odeme_tutari`	Yes
`girilen_tutar`	Yes
`stopaj_tutari`	Yes
`kdv_orani_yuzde`	No
`stopaj_orani_yuzde`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true, making the tool non-destructive. The description adds that it calculates with user-given rate and handles brut/net and optional VAT. No side effects, auth needs, or rate limits mentioned; but for a calculation tool, this is adequate. No contradiction with annotations.

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?

Description is a single concise sentence that front-loads the main action. It is not verbose, but could benefit from slight restructuring to include key details without increasing length significantly.

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?

Tool has output schema but the description does not mention what is returned (e.g., calculated amounts). It does not state that 'tutar_tipi' defaults to 'brut' or that 'kdv_orani' is optional. For a calculation tool with 4 parameters, this description is too sparse to be fully complete.

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

Parameters2/5

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

Schema coverage is 0% (no parameter descriptions), so the description must compensate. It mentions 'oran' and 'brut/net stopaj' but does not explain 'tutar', 'tutar_tipi' (enum brut/net), 'kdv_orani' (optional), or 'stopaj_orani' beyond the rate. Insufficient for a tool with 4 parameters.

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

Purpose5/5

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

Description clearly states the verb 'hesaplar' (calculates) and the resource: 'brut/net stopaj ve opsiyonel KDV' (gross/net withholding tax and optional VAT). This is specific and distinguishes it from siblings like 'kdv_hesapla' (only VAT) and 'gecikme_zammi_hesapla' (delay interest).

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?

The description implies usage for stopaj calculation but provides no explicit guidance on when to use this tool versus alternatives like 'kdv_hesapla' for pure VAT or 'gecikme_zammi_hesapla' for delay interest. No exclusions or when-not-to-use instructions.

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

Deploy Server