Skip to main content
Glama

ders_programi

Read-onlyIdempotent

Retrieves a course's curriculum page with its program PDF, grade levels, and related textbooks by course slug or name.

Instructions

Bir dersin öğretim programı sayfasını getirir: program PDF'i, sınıf seviyeleri (sinif_id) ve derse ait kitaplar.

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

Input Schema

NameRequiredDescriptionDefault
dersYesders_slug (ör. 'kimya-dersi') ya da ders adı.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 the safety profile is covered. The description adds that the response bundles a PDF, grade-level identifiers and book entries — useful payload context — but says nothing about failure behavior for an unknown course or about PDF retrieval/linking.

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 front-loaded sentence with the action first and the returned fields enumerated after a colon; no filler and nothing an agent has to skim past.

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?

The tool is simple (one required param, has an output schema), and the description still names the three payload components, which fully covers what an agent needs to decide and call. Only the relationship to ders_ara and to the sinif_id-consuming siblings is left unstated.

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 defines 'ders' as a slug (e.g. 'kimya-dersi') or a course name, so the description adds essentially no param meaning beyond it. Baseline 3 applies.

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 (getirir) plus resource (öğretim programı sayfası) and even enumerates the payload: program PDF, sınıf seviyeleri (sinif_id), and the course's books. It does not, however, name or contrast the sibling search tool (ders_ara), so an agent must infer that this is the detail-level fetch rather than the search entry point.

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?

Usage is only implied: the parameter note 'ders_slug ya da ders adı' hints that an agent can call it directly without first searching, and the returned sinif_id hints it feeds the class-level tools, but there is no explicit when-to-use/when-not statement or named alternative.

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