Skip to main content
Glama

Get book page

turath_get_page
Read-only

Fetches the text of a single book page from the Turath Islamic library using a book ID and page number, so you can read or extract specific page content.

Instructions

Fetch the text of one page of a book.

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>",
      "page": "<page>"
    },
    "name": "turath_get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage number
book_idYesBook ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds no behavioral context of its own. It does not say what happens for an out-of-range or nonexistent page, whether page numbering starts at 1, or what form the returned text takes, which is exactly the kind of detail the description is supposed to supply.

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?

A single short sentence, front-loaded with the verb and containing no filler. It is efficient, though the brevity borders on under-specification rather than crispness.

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?

For a two-parameter read tool with a fully documented schema and annotations covering safety, the description is minimally sufficient. It leaves open edge-case behavior (invalid page, missing book) that an agent calling this tool would plausibly need, and there is no output schema to compensate.

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%: both book_id and page are documented as positive integers in the schema, so the description has little room to add value. It does clarify the unit of the 'page' parameter as one page of text, but gives no semantics for book_id resolution or page-number origin. Baseline 3 applies when the schema does the heavy lifting.

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 ("Fetch the text of one page of a book"), which is clearly distinct from turath_get_book and the plural turath_get_pages. It stops short of explicitly contrasting itself with those siblings, so an agent must infer the single-page vs. multi-page split from the word "one".

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?

Usage is only implied: "one page" hints that bulk retrieval belongs to turath_get_pages or turath_get_pages, but the description never says when to choose this tool or when to avoid it. There is no guidance on prerequisites such as needing a valid book_id first, nor on alternatives like turath_summarize_page.

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