Skip to main content
Glama

Get a range of pages

turath_get_pages
Read-only

Retrieve up to 10 consecutive pages from a book in a single request by specifying book ID and page range. Use it to read sequential sections without multiple calls.

Instructions

Fetch up to 10 consecutive pages of a book in one call.

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": {
      "book_id": "<book_id>",
      "from_page": "<from_page>",
      "to_page": "<to_page>"
    },
    "name": "turath_get_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYesBook ID
to_pageYesLast page (max 10 pages from from_page)
from_pageYesFirst page

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish that this is a read-only and open-world operation, so the description does not need to explain safety. It adds the meaningful constraint that the call fetches up to 10 consecutive pages at once, but it does not describe error behavior, ordering, or return details.

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 definition is a single, front-loaded sentence with no unnecessary wording. Every phrase contributes to describing the resource and its range constraint.

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 simple three-parameter fetch tool with full schema coverage and annotations, the description is largely complete for selecting and invoking it. It could be stronger if it clarified return format or edge cases such as attempting to fetch more than the allowed page range, but those are minor for this tool's complexity.

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 book_id, from_page, and to_page are already fully documented. The description reinforces that the pages are consecutive and capped at 10, but it adds little parameter meaning beyond the schema itself.

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 uses a specific verb, "Fetch," and resource, "up to 10 consecutive pages of a book," so the operation and scope are clear. It does not explicitly distinguish itself from related tools such as turath_get_page or turath_export_pages, which keeps it from a 5.

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?

It implies this tool should be used when multiple consecutive pages are needed in one call, but it gives no explicit guidance about when to use it instead of turath_get_page or turath_export_pages. The usage context is inferable but not stated.

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