YokTez MCP

List Yok Tez Anabilim Dali

list_yok_tez_anabilim_dali

Find YÖK department (Anabilim Dalı) names and codes by keyword. Use the returned codes to search theses via search_yok_tez_by_anabilim_dali, since regular keyword search cannot search inside department names.

Instructions

Find YÖK departments (Anabilim Dalı) whose name contains a keyword.

YÖK's regular keyword search canNOT search inside department names. Use this tool first to discover the relevant departments and their codes, then pass the codes you want to 'search_yok_tez_by_anabilim_dali' to retrieve theses from those departments.

Example: keyword='hukuk' returns departments like 'KAMU HUKUKU ANABİLİM DALI' (code 41), 'TİCARET HUKUKU ANABİLİM DALI' (code 906), etc. The LLM can then pick one or several codes to search.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`keyword`	Yes	A word to look for inside department (anabilim dalı) names, e.g. 'hukuk', 'bilgisayar', 'tarih'. Matching is case-insensitive and Turkish-aware.
`max_results`	No	Maximum number of matching departments to return.

Output Schema

TableJSON Schema

Name	Required	Description
`keyword`	No	The keyword that was matched against department names.
`matches`	No	Departments whose name contains the keyword (name + code pairs).
`returned`	No	Number of matches actually returned (may be capped by max_results).
`error_message`	No	Error message if the list could not be fetched or no match was found.
`total_matches`	No	Total number of departments matching the keyword.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A4.7/5.0

Behavior4/5

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

No annotations are provided, but the description and schema make the read-only lookup behavior clear: name matching is case-insensitive and Turkish-aware, with max_results capping results. It does not explicitly say 'read-only' or describe data freshness, but this is a simple list/search operation.

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?

Three short paragraphs: purpose, workflow, concrete example. No redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and the description is complete: how the keyword match works, how to bound results, and how to proceed to the next step using the returned codes. The output schema, if present, can define exact result fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both parameters have meaningful descriptions. The description adds value by giving an example and clarifying Turkish-aware matching, going beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action and resource: finding YÖK departments by keyword. It also distinguishes itself from sibling search tools by explaining that regular keyword search cannot search inside department names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clear when to use: use this first to discover department codes, then pass those codes to search_yok_tez_by_anabilim_dali. The example with 'hukuk' makes the workflow concrete.

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

Deploy Server