Skip to main content
Glama

Sınav neti

sinav_neti_hesapla
Read-onlyIdempotent

Çoktan seçmeli sınavda neti ve yüzde başarıyı hesaplar. dogru + yanlis toplamSoru'yu geçemez; boşlar yanlış sayılmaz. YKS ve LGS için kendi araçlarını kullanın.

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": {
      "dogru": "<dogru>",
      "yanlis": "<yanlis>",
      "toplamSoru": "<toplamSoru>"
    },
    "name": "sinav_neti_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
dogruYesDoğru sayısı (0 ya da pozitif; dogru + yanlis ≤ toplamSoru).
yanlisYesYanlış sayısı (0 ya da pozitif; dogru + yanlis ≤ toplamSoru). Boşlar yanlış sayılmaz.
toplamSoruYesSınavdaki toplam soru sayısı (boşlar dahil).
kacYanlisBirDogruNoKaç yanlışın bir doğruyu götürdüğü (ör. 4; LGS için 3). Varsayılan 4.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / dogru / description
      Previous value: -"Doğru sayısı."New value: +"Doğru sayısı (0 ya da pozitif; dogru + yanlis ≤ toplamSoru)."
    • changedInput schema / properties / toplamSoru / description
      Previous value: -"Toplam soru sayısı."New value: +"Sınavdaki toplam soru sayısı (boşlar dahil)."
    • changedInput schema / properties / yanlis / description
      Previous value: -"Yanlış sayısı."New value: +"Yanlış sayısı (0 ya da pozitif; dogru + yanlis ≤ toplamSoru). Boşlar yanlış sayılmaz."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing a validation invariant (dogru + yanlis cannot exceed toplamSoru) and an edge-case rule (blanks are not counted as wrong), but it never states the actual net formula or how the divisor parameter affects the result.

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?

Three short sentences with zero filler: purpose first, then the validity constraint, then the routing note. Every sentence carries distinct information an agent needs.

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 simple pure-calculation tool with full annotation coverage and complete schema documentation, the definition covers purpose, constraints and alternatives. The only gap is that without an output schema it does not spell out the returned fields beyond 'net' and 'yüzde başarı', which is minor.

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%, with each of the four parameters documented, including the default of 4 for kacYanlisBirDogru. The description reinforces the blanks-are-not-wrong rule but adds no new syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: computes net score and percentage success for a multiple-choice exam. It also explicitly carves out YKS and LGS, which are handled by dedicated sibling tools such as lgs_puani_hesapla, so an agent can distinguish this generic calculator from the exam-specific ones.

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

Usage Guidelines4/5

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

Gives a clear usage context (generic multiple-choice exams) plus an explicit exclusion pointing YKS/LGS callers to other tools. The exclusion is vague about which tool ('kendi araçlarını kullanın') rather than naming the sibling, so it falls short of a full 5.

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