Skip to main content
Glama

ders_ara

Read-onlyIdempotent

Search courses with curriculum data by course name and/or grade level, returning the course slug needed to retrieve curriculum details, units, and learning outcomes.

Instructions

Öğretim programı bulunan dersleri ada ve/veya kademeye göre arar.

Dönen ders_slug değeri ders_programi, uniteleri_listele ve ogrenme_ciktilari araçlarında kullanılır.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ders_ara"
  }
}

Input Schema

NameRequiredDescriptionDefault
sorguNoDers adında aranacak kelime(ler), ör. 'matematik', 'kimya'. Boş bırakılırsa tümü listelenir.
kademeNoKademe kimliği, slug'ı ya da adı (ör. '3', 'ortaogretim', 'Temel Eğitim').

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and open-world behavior, so the bar is lower. The description still adds real value by disclosing the implicit filter (only courses with a curriculum) and by explaining the downstream role of the ders_slug output, which annotations cannot convey.

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 short sentences, front-loaded with the action and followed by the chaining hint. No filler or 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?

An output schema exists, so return values need not be explained, and the description correctly focuses on the one output field that matters for chaining. For a two-optional-parameter search tool this is nearly complete, missing only explicit sibling differentiation.

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 both parameters are already fully documented with examples. The description only restates the name/level axes ('ada ve/veya kademeye göre') without adding format or matching semantics beyond the schema, so the 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?

The description states a specific verb and resource ('Öğretim programı bulunan dersleri ... arar') and adds a scoping constraint (only courses that have a curriculum). It does not explicitly contrast with siblings like sinifa_gore_dersler, but the name/level search axis is clear enough to distinguish it.

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?

It gives a concrete workflow cue: the returned ders_slug feeds ders_programi, uniteleri_listele and ogrenme_ciktilari, which tells the agent when to reach for this tool first. It stops short of stating when not to use it or how it differs from the class-based sibling.

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