Skip to main content
Glama

sinifa_gore_dersler

Read-onlyIdempotent

Lists courses available at a specified education level and class, with curriculum PDF links for each course.

Instructions

Belirli bir kademe ve sınıf seviyesinde öğretim programı olan dersleri, program PDF bağlantılarıyla listeler.

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": {
      "kademe": "<kademe>",
      "sinif_id": "<sinif_id>"
    },
    "name": "sinifa_gore_dersler"
  }
}

Input Schema

NameRequiredDescriptionDefault
kademeYesKademe kimliği, slug'ı ya da adı (ör. '2' ya da 'temel-egitim').
sinif_idYesSınıf kimliği (kademeleri_listele ile öğrenilir; ör. 5.Sınıf=6, 10.Sınıf=12).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds the useful behavioral fact that results include program PDF links, but says nothing about pagination, result volume, or what happens when a grade has no curriculum.

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

Conciseness4/5

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

A single sentence with no filler, and the central action ('listeler') arrives before the qualifying clause. It is tight and front-loaded, with no redundant restatement of the tool name.

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?

With full schema coverage, an output schema, and rich annotations, the definition supplies everything needed to invoke the tool correctly. The remaining gap is purely navigational: it does not direct the agent to this tool over its siblings.

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%, so the schema already explains kademe (slug/name/id) and sinif_id (with examples and the hint to use kademeleri_listele). The description only restates that both are filters, adding no format or edge-case meaning beyond the schema; the 3 baseline 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?

The description uses a specific verb+resource pairing ('öğretim programı olan dersleri ... listeler') and scopes it to a kademe and sınıf seviyesi, plus notes the output carries curriculum PDF links. It is clear what the tool returns, though it never names or contrasts itself with siblings such as ders_ara or ders_programi.

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 agent can infer it applies when it has a kademe and a sınıf_id and wants the courses with a curriculum at that level. There is no explicit when-to-use vs. when-not guidance and no pointer to the alternative tools for searching courses or fetching a single curriculum.

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