Skip to main content
Glama

ogrenme_ciktilari

Read-onlyIdempotent

Retrieves all learning outcomes and class hours for every unit of a course at a given grade level in one request, supporting annual planning, outcome lists, and assessment design.

Instructions

Bir dersin bir sınıf seviyesindeki TÜM ünitelerinin öğrenme çıktılarını ve ders saatlerini tek seferde getirir.

Yıllık plan, kazanım listesi ya da ölçme aracı hazırlarken kullanışlıdır.

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": {
      "ders": "<ders>",
      "sinif_id": "<sinif_id>"
    },
    "name": "ogrenme_ciktilari"
  }
}

Input Schema

NameRequiredDescriptionDefault
dersYesders_slug (ör. 'matematik-dersi') ya da ders adı.
sinif_idYesSınıf kimliği (ders_programi aracı dersin sınıflarını verir).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: the call returns complete coverage across all units "tek seferde" (in one shot), implying no pagination or per-unit looping is needed. Missing are ordering, response size, or error behavior, but an output schema exists to carry the return shape.

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?

Two sentences, zero filler, with the capability and its completeness guarantee front-loaded before the use case. Nothing repeats the title or the schema.

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?

Given a two-parameter, read-only tool with full schema descriptions and an output schema, the definition covers what it returns, at what granularity, and for what purpose. The only gap is an explicit pointer to sibling tools for single-unit or list-level needs.

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 coverage is 100%, and the schema itself already explains that ders accepts a slug or a course name and that sinif_id comes from ders_programi. The description adds no further meaning about either parameter, 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?

Specific verb ("getirir") plus a precisely scoped resource: the learning outcomes AND course hours of ALL units of one course at one grade level. The emphasis on "TÜM ünitelerinin" and "tek seferde" implicitly separates it from unit-level siblings such as unite_detay and uniteleri_listele, so an agent can pick it without inspecting schemas.

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?

The second sentence gives a concrete use context: preparing an annual plan, a list of attainments, or an assessment instrument. It states no exclusions or named alternatives, so the agent must still infer that single-unit lookups belong to unite_detay, but the when-to-use signal is clear.

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