YokTez MCP

Get Yok Tez Document Markdown

get_yok_tez_document_markdown

Retrieve a specific YÖK thesis page as Markdown by providing its detail page URL and optional page number. Downloads the PDF, extracts the requested page, and converts it to readable text for further analysis.

Instructions

Retrieves a specific YÖK thesis PDF using its detail page URL. It fetches metadata from the detail page, downloads the PDF (if permissible and not cached), isolates the specified PDF page, converts that page to Markdown, and returns the content.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page_number`	No	The PDF page number (1-based) for which to retrieve Markdown content. Default is 1.
`detail_page_url`	Yes	The detail page URL of the thesis on YÖK Tez Merkezi. This URL is usually obtained from the 'search_yok_tez_detailed' tool results.

Output Schema

TableJSON Schema

Name	Required	Description
`is_paginated`	Yes	True if the PDF has more than one page.
`thesis_title`	No	Title of the thesis (Turkish), extracted from the detail page.
`error_message`	No	Error message if document retrieval or processing failed.
`thesis_author`	No	Author of the thesis, extracted from the detail page.
`total_pdf_pages`	Yes	Total number of pages in the original PDF.
`current_pdf_page`	Yes	The PDF page number returned.
`retrieved_pdf_url`	No	The actual URL the PDF was downloaded from.
`characters_on_page`	No	Number of characters in the page's Markdown content.
`page_markdown_content`	No	Markdown content of the requested PDF page. Null if extraction failed.
`source_detail_page_url`	Yes	The source YÖK Tez detail page URL the PDF was processed from.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the transparency burden and reveals the pipeline: fetch metadata, download PDF if permissible and not cached, isolate the page, and convert to Markdown. It does not mention failure modes or side effects, but the read-only, network-dependent behavior is reasonably disclosed.

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?

The description is two sentences and directly states the action and process without irrelevant detail. Parameter descriptions are also concise and tied to usage.

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 description includes the required input source and the output concept (Markdown content of a specific page), which is sufficient given that an output schema is indicated. It could be slightly more explicit about what happens when the PDF is not permissible or not found, but that is not necessary for invocation.

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

Parameters5/5

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

Both parameters have descriptions that add context beyond the schema: page_number is 1-based with a default, and detail_page_url explains its source and format. Schema description coverage is 100%.

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: retrieving a YÖK thesis PDF page via its detail page URL and returning Markdown content. It distinguishes from sibling tools by focusing on document page content rather than search or thesis metadata.

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 explains that the detail_page_url should come from search_yok_tez_detailed and that page_number selects the page, giving clear usage context. It does not explicitly name alternatives such as get_yok_tez_thesis_details for metadata, so exclusions are only implied.

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

Deploy Server