Skip to main content
Glama

kitap_detay

Read-onlyIdempotent

Fetches details for a textbook by ID, including grade/course/level tags, update date, PDF link, and interactive book link.

Instructions

Bir kitabın ayrıntılarını getirir: sınıf/ders/kademe etiketleri, güncelleme tarihi, PDF ve etkileşimli kitap bağlantısı.

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": {
      "kitap_id": "<kitap_id>"
    },
    "name": "kitap_detay"
  }
}

Input Schema

NameRequiredDescriptionDefault
kitap_idYesKitap kimliği (kitap_ara ya da ders_programi çıktısından).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 profile is covered. The description adds some behavioral context by implying external PDF/interactive links are returned, but says nothing about failures for invalid ids or any access constraints. It does not contradict the annotations.

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?

One compact sentence with the purpose front-loaded and no filler wording. It is efficiently sized, though the content it does include leans on return-value enumeration rather than decision guidance.

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

Completeness3/5

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

With an output schema present, spelling out the returned fields is largely redundant, and the description omits the usage/routing information that would actually help an agent choose this tool. For a simple one-parameter read operation with full schema and annotation coverage, this is adequate but leaves a clear gap.

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?

There is a single parameter and the schema description coverage is 100%, including the note that kitap_id comes from kitap_ara or ders_programi output. The description adds no parameter meaning beyond the schema, so the baseline of 3 for high-coverage schemas 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 names a specific verb and resource ('Bir kitabın ayrıntılarını getirir') and enumerates the concrete fields returned (grade/subject/level tags, update date, PDF and interactive book links). It is clearly a detail-lookup tool, but it never distinguishes itself from siblings such as kitap_ara or unite_detay, so an agent must infer the boundary.

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

Usage Guidelines2/5

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

The description gives no when-to-use, when-not-to-use, or alternative routing guidance. The only workflow hint ('kitap_ara ya da ders_programi çıktısından') lives in the parameter schema, not the description, and nothing tells the agent when to prefer this over kitap_ara.

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