Skip to main content
Glama

kitap_ara

Read-onlyIdempotent

Search textbooks, teacher guides, workbooks, and activity books by title, grade, or course, then return PDF and interactive book links for each match.

Instructions

Ders kitapları, öğretmen kılavuz kitapları, çalışma kitapları ve etkinlik kitapları arasında arama yapar.

Her sonuç için PDF ve (varsa) etkileşimli kitap bağlantısı döner.

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": "kitap_ara"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEn fazla kaç sonuç döneceği.
sorguNoKitap adında aranacak kelimeler, ör. 'fizik 10', 'öğretmen kılavuz', 'çalışma kitabı'.
kademeNoKademe kimliği, slug'ı ya da adı.
ders_idNoDers kimliği (ders_ara/sinifa_gore_dersler çıktısındaki ders_id).
sinif_idNoSınıf kimliği (ör. 9.Sınıf=11).

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?

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety and repeatability profile is covered structurally. The description adds that each result yields a PDF link plus an optional interactive-book link, which is useful behavioral context, but it says nothing about result ordering, paging behavior, or what happens with zero matches. Given annotation coverage, a 3 is appropriate.

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?

Two short sentences with the search scope front-loaded and the return shape second; nothing is wasted or buried. It could be marginally tighter, but the structure serves the reader well.

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 five optional parameters, an output schema present, and annotations covering safety, the description only needs to establish purpose and scope — which it does. The remaining gap is guidance on combining the optional filters, which the schema partially covers on its own.

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 every parameter (limit, sorgu, kademe, ders_id, sinif_id, including the 9.Sınıf=11 example) is already self-documented. The description contributes no additional meaning about how these filters interact or which combinations are meaningful, so it sits at the baseline.

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 ('arama yapar' over ders kitapları, öğretmen kılavuz, çalışma ve etkinlik kitapları) and enumerates the content types searched, so an agent knows exactly what corpus this covers. It stops short of naming how it differs from siblings like kitap_detay or ders_ara, so it is clear but not fully differentiated.

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 by the enumeration of book types; there is no explicit statement of when to reach for this tool versus kitap_detay (detail) or ders_ara (subject lookup), and no guidance on whether filters can/should be combined. An agent can infer the search intent from the name and description, but nothing is stated outright.

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