Skip to main content
Glama

Get book info

turath_get_book
Read-only

Retrieves a book's metadata from the Turath Islamic library by ID, optionally including its table of contents.

Instructions

Book metadata, optionally with its table of contents (indexes).

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

Input Schema

NameRequiredDescriptionDefault
book_idYesBook ID
include_indexesNoInclude table of contents (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds almost nothing beyond them: it does not say what fields the metadata contains, how large a table of contents may be, or whether indexes are expensive to fetch, which is the main behavioral question for a read tool with an optional expansion.

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 with no filler, and the core resource is front-loaded. It reads as a fragment rather than a structured statement, so it is efficient but slightly under-formed.

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 simple two-parameter read tool with full schema coverage and no output schema, this is minimally adequate. The notable gap is that an agent cannot tell what the returned metadata consists of or when including indexes is worthwhile, which matters for an openWorld read operation.

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 coverage is 100%, so both book_id and include_indexes are already documented, including the default. The description reinforces that 'indexes' means table of contents, adding marginal clarification, but supplies no further meaning beyond the schema — baseline 3 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 the resource (book metadata) and the optional extra (table of contents / indexes), which is enough for an agent to know this returns book-level info keyed by book_id. It does not use an explicit verb and does not explicitly distinguish itself from siblings like turath_get_book_file or turath_get_page, but the resource is clear.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative for related tasks (e.g., fetching files or pages). The only usage signal is the word 'optionally' attached to indexes, which is inferred rather than stated as a rule.

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