Skip to main content
Glama

Vize-final ortalaması

vize_final_ortalamasi_hesapla
Read-onlyIdempotent

Vize ve finalden ağırlıklı ortalamayı hesaplar; final verilmezse geçmek için gereken final notunu bulur.

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": {
      "vize": "<vize>"
    },
    "name": "vize_final_ortalamasi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
vizeYes0-100.
finalNo0-100. Boşsa gereken final notu bulunur.
gecmeNotuNoGeçme notu. Varsayılan 50.
vizeAgirlikNo%. Varsayılan 40.
finalAgirlikNo%. Varsayılan 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / final / description
      Previous value: -"Final notu (0-100). Bilinmiyorsa boş: gereken final notu hesaplanır."New value: +"0-100. Boşsa gereken final notu bulunur."
    • changedInput schema / properties / finalAgirlik / description
      Previous value: -"Finalin ağırlığı (%). Varsayılan 60."New value: +"%. Varsayılan 60."
    • changedInput schema / properties / vize / description
      Previous value: -"Vize notu (0-100)."New value: +"0-100."
    • changedInput schema / properties / vizeAgirlik / description
      Previous value: -"Vizenin ağırlığı (%). Varsayılan 40."New value: +"%. Varsayılan 40."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral context beyond them: the inverse computation triggered by omitting the final grade, which an agent would not otherwise anticipate. It stops short of describing what the response contains (average only vs. pass/fail verdict) or how the weights are combined.

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?

A single well-formed sentence that front-loads the primary operation and appends the conditional variant after a semicolon. No filler, no redundancy.

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 deterministic calculator with full schema coverage and no output schema, the description covers both execution paths adequately. The only real gap is the shape of the result for each mode, which matters moderately for a dual-mode tool.

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 every parameter including defaults documented in-schema, so the baseline is 3. The description's mention of the optional final mirrors what the schema already states and adds no new detail on the weight parameters or how vizeAgirlik/finalAgirlik interact.

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 a specific verb (hesaplar) and resource (vize ve final ağırlıklı ortalama) and additionally discloses a second mode (finding the required final grade when the final is absent). The exam-grade domain is distinct enough from the sibling calculators that an agent can place it without opening the schema, though no sibling is named explicitly.

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?

"final verilmezse geçmek için gereken final notunu bulur" gives clear conditional guidance for the two modes of this tool, which is genuinely useful for choosing how to fill the parameters. However, there is no guidance on when to prefer this tool over adjacent siblings such as sinav_neti_hesapla, and no stated preconditions or exclusions.

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