Skip to main content
Glama

unite_detay

Read-onlyIdempotent

Retrieves curriculum content by course and unit ID, covering learning outcomes, skills, values, assessments, and teaching practices, with optional filtering by section.

Instructions

Bir ünite/temanın tüm program içeriğini getirir.

İçerik: ders saati, alan/kavramsal beceriler, eğilimler, programlar arası bileşenler (SDB, değerler, okuryazarlık), öğrenme çıktıları ve süreç bileşenleri, içerik çerçevesi, anahtar kavramlar, ölçme-değerlendirme, öğrenme-öğretme uygulamaları, zenginleştirme ve destekleme.

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>",
      "unite_id": "<unite_id>"
    },
    "name": "unite_detay"
  }
}

Input Schema

NameRequiredDescriptionDefault
dersYesders_slug (ör. 'kimya-dersi') ya da ders adı.
bolumlerNoİsteğe bağlı: yalnızca bu bölümleri getir (başlıkta geçen kelimeyle eşleşir). Örn. ['Öğrenme Çıktıları', 'Ders Saati', 'Anahtar Kavramlar', 'İçerik Çerçevesi', 'Alan Becerileri', 'Öğrenme Kanıtları', 'Öğrenme-Öğretme Uygulamaları', 'Farklılaştırma']. Boş bırakılırsa tüm bölümler gelir.
unite_idYesÜnite/tema kimliği (uniteleri_listele ile öğrenilir).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotency are covered without the prose. What the description adds is a preview of returned content, but it says nothing about response size, latency, or partial-failure behavior for a read that pulls an entire curriculum unit — a real concern for a 'tüm içerik' call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The one-line purpose statement is well front-loaded, but the eight-item content enumeration largely restates what the existing output schema already conveys and is the bulk of the text. It reads as a payload listing rather than decision-supporting information, so several lines do not earn their place.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile, so the essentials are in place. The remaining gap is routing: with closely related siblings (uniteleri_listele, ders_programi, ogrenme_ciktilari) an agent still has to guess when this detail call is the right choice.

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% and all three parameters are documented in-schema, including the ders slug/name duality and the bolumler section-matching semantics with worked examples. The description adds nothing beyond the schema here, so the baseline 3 is correct.

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 opens with a concrete verb+resource pair: 'Bir ünite/temanın tüm program içeriğini getirir' — retrieval of a unit's full curriculum content — and then enumerates what that content comprises. An agent can tell this is the detailed counterpart to a unit-listing tool, though no sibling is named explicitly, so the differentiation stays implicit.

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 phrase 'tüm program içeriğini getirir' implies this is the full-detail fetch, and the schema's bolumler parameter hints that narrower fetches exist. But the description itself never says when to prefer this over sisters like ders_programi, ogrenme_ciktilari or uniteleri_listele, and offers no prerequisites or exclusions — usage is only implied.

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