Skip to main content
Glama

Trafik cezası erken ödeme

trafik_cezasi_erken_odeme_hesapla
Read-onlyIdempotent

Trafik cezası erken ödeme indirimi: tebliğden bir ay içinde ödenirse %25 indirim (Kabahatler Kanunu md. 17/6).

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": {
      "cezaTutari": "<cezaTutari>"
    },
    "name": "trafik_cezasi_erken_odeme_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
cezaTutariYesTutanaktaki tutar (TL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cezaTutari / description
      Previous value: -"Ceza tutanağındaki tutar (TL)."New value: +"Tutanaktaki tutar (TL)."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safe, read-only, idempotent, closed-world profile, so the description's job is to add behavioral context. It does add real value by disclosing the 25% rate and its legal basis, but it says nothing about the returned figures (discounted amount only, or also the discount/savings), rounding, or whether out-of-period input is rejected or treated as no discount.

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?

One compact sentence, front-loaded with the subject and the discount rate, with the legal citation placed at the end where it belongs. It contains no filler; the only shortfall is that brevity comes at the cost of any output or edge-case framing.

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 one-parameter calculator with no output schema, the description conveys the core formula but not the result shape an agent will receive or the behavior for payments beyond the one-month deadline. It is adequate to select the tool but leaves the invocation's outcome somewhat unpredictable.

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?

There is a single required parameter with 100% schema description coverage ('Tutanaktaki tutar (TL)', exclusiveMinimum 0), so the schema already carries the semantics. The description adds nothing about the parameter, e.g. whether the amount must be the full pre-discount fine rather than an already-discounted figure; baseline 3 applies.

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 exact subject (trafik cezası erken ödeme indirimi) and states the substantive rule the tool applies: 25% discount if paid within one month of notification, citing Kabahatler Kanunu md. 17/6. This distinguishes it cleanly from the sibling calculators (kredi, kira, kdv, etc.), though it never uses an explicit verb such as 'calculates' to say what the tool produces.

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 through the legal condition 'tebliğden bir ay içinde ödenirse', which tells the agent the scenario in which the discount applies. There is no explicit statement of when to call this tool versus another, and no guidance on what happens if the payment falls outside the one-month window.

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