Skip to main content
Glama

sayfa_oku

Read-onlyIdempotent

Reads the main content of any tymm.meb.gov.tr page as plain text or Markdown, enabling extraction of curriculum skill definitions, model explanations, guides, and material lists.

Instructions

tymm.meb.gov.tr üzerindeki herhangi bir sayfanın ana içeriğini düz metin/Markdown olarak okur.

Beceri tanımları (KB, E, SDB, OB, D kodları), model açıklamaları, kılavuz ve materyal listeleri için kullanılır.

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": {
      "yol": "<yol>"
    },
    "name": "sayfa_oku"
  }
}

Input Schema

NameRequiredDescriptionDefault
yolYesSayfa yolu ya da tam URL, ör. '/beceriler/kavramsal-beceriler' veya 'https://tymm.meb.gov.tr/genel-bakis'.
baslangicNoUzun sayfalarda metnin kaçıncı karakterinden başlanacağı.
max_karakterNoDöndürülecek en fazla karakter sayısı.

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/openWorld/idempotent, so the safety profile is covered; the description adds that only the *main* content is extracted (implying navigation/boilerplate is stripped) and that output is plain text/Markdown. It does not mention that long pages are truncated or paged, which the schema covers only implicitly.

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 sentences, purpose first, usage second, no filler. Everything is front-loaded and nothing is redundant.

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?

For a read-only page-fetch tool with a full input schema and an output schema, the description covers scope, format, and typical targets. The only gap is that truncation/paging of long pages is not hinted at in prose.

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% and the three parameters (path/URL, start offset, max characters) are fully documented in the schema itself. The description adds no extra semantics about path format or paging behavior, so the 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?

States a specific verb (okur/reads) and resource (any page's main content on tymm.meb.gov.tr) plus the output format (plain text/Markdown). It is clearly a content-fetch tool, though it never names or contrasts with the 'sayfalari_listele' sibling that an agent might confuse it with.

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?

The second sentence gives concrete usage contexts (skill definitions with KB/E/SDB/OB/D codes, model explanations, guide and material lists), which is genuine when-to-use guidance. It stops short of stating exclusions or naming alternatives, so it is clear context without routing.

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