Skip to main content
Glama

LGS puanı

lgs_puani_hesapla
Read-onlyIdempotent

2026 LGS: ders bazında doğru/yanlıştan netleri (3 yanlış 1 doğruyu götürür) ve tahmini puanı (MEB standart puan yöntemi) 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": {
      "turkceDogru": "<turkceDogru>",
      "inkilapDogru": "<inkilapDogru>",
      "dinDogru": "<dinDogru>",
      "yabanciDilDogru": "<yabanciDilDogru>",
      "matematikDogru": "<matematikDogru>",
      "fenDogru": "<fenDogru>"
    },
    "name": "lgs_puani_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
dinDogruYesDin Kültürü doğru (10 soru).
fenDogruYesFen Bilimleri doğru (20 soru).
dinYanlisNoVarsayılan 0.
fenYanlisNoVarsayılan 0.
turkceDogruYesTürkçe doğru (20 soru).
inkilapDogruYesİnkılap Tarihi doğru (10 soru).
turkceYanlisNoVarsayılan 0.
inkilapYanlisNoVarsayılan 0.
matematikDogruYesMatematik doğru (20 soru).
matematikYanlisNoVarsayılan 0.
yabanciDilDogruYesYabancı Dil doğru (10 soru).
yabanciDilYanlisNoVarsayılan 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changed
    • changedInput schema / properties / dinDogru / description
      Previous value: -"Din Kültürü doğru sayısı (10 soru)."New value: +"Din Kültürü doğru (10 soru)."
    • changedInput schema / properties / dinYanlis / description
      Previous value: -"Din Kültürü yanlış sayısı. Varsayılan 0."New value: +"Varsayılan 0."
    • changedInput schema / properties / fenDogru / description
      Previous value: -"Fen Bilimleri doğru sayısı (20 soru)."New value: +"Fen Bilimleri doğru (20 soru)."
    • changedInput schema / properties / fenYanlis / description
      Previous value: -"Fen Bilimleri yanlış sayısı. Varsayılan 0."New value: +"Varsayılan 0."
    • changedInput schema / properties / inkilapDogru / description
      Previous value: -"İnkılap Tarihi doğru sayısı (10 soru)."New value: +"İnkılap Tarihi doğru (10 soru)."
    • changedInput schema / properties / inkilapYanlis / description
      Previous value: -"İnkılap Tarihi yanlış sayısı. Varsayılan 0."New value: +"Varsayılan 0."
    • changedInput schema / properties / matematikDogru / description
      Previous value: -"Matematik doğru sayısı (20 soru)."New value: +"Matematik doğru (20 soru)."
    • changedInput schema / properties / matematikYanlis / description
      Previous value: -"Matematik yanlış sayısı. Varsayılan 0."New value: +"Varsayılan 0."
    • changedInput schema / properties / turkceDogru / description
      Previous value: -"Türkçe doğru sayısı (20 soru)."New value: +"Türkçe doğru (20 soru)."
    • changedInput schema / properties / turkceYanlis / description
      Previous value: -"Türkçe yanlış sayısı. Varsayılan 0."New value: +"Varsayılan 0."
    • changedInput schema / properties / yabanciDilDogru / description
      Previous value: -"Yabancı Dil doğru sayısı (10 soru)."New value: +"Yabancı Dil doğru (10 soru)."
    • changedInput schema / properties / yabanciDilYanlis / description
      Previous value: -"Yabancı Dil yanlış sayısı. Varsayılan 0."New value: +"Varsayılan 0."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description does add genuinely useful behavior context — the 3-wrong-cancels-1-right net rule, the MEB standard-score method, and the word 'tahmini' signalling the result is an estimate rather than an official score. It still says nothing about the shape of the returned values despite there being no output schema.

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 dense sentence with no filler, and the year and scope are front-loaded before the calculation semantics. Slightly heavy parenthetical stacking, but nothing is wasted.

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

Completeness4/5

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

For a 12-parameter, 6-required calculator with fully described schema fields and no output schema, the description covers purpose, method, and the estimation caveat. What is missing is minor: expected return contents and the treatment of optional yanlis fields (the schema carries the default but the description does not reinforce it).

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 is 3, but the description adds a computation rule not present in the schema: wrong answers reduce the net at a 3:1 ratio, which tells the agent how yanlis parameters are actually consumed. It does not, however, restate that yanlis fields default to 0 or how omitted subjects are handled.

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?

States a specific verb (hesaplar) and a specific resource (LGS ders bazında netler ve tahmini puan) and pins the year to 2026. It is clearly the LGS-scoped calculator rather than a generic exam tool, though it never explicitly contrasts itself with the sibling sinav_neti_hesapla.

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 mention of '2026 LGS' implies the applicable context, and the scoring rule implies input expectations, but there is no explicit when-to-use/when-not statement and no routing guidance versus sinav_neti_hesapla or yks_puani_hesapla. Usage is inferable rather than stated.

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