Skip to main content
Glama

Summarize a book page (uses client sampling)

turath_summarize_page
Read-only

Fetches a Turath library book page and asks the client's model to summarize it in the selected language; requires client sampling support.

Instructions

Fetches a page and asks the client's own model to summarize it. Requires a client with sampling support.

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_summarize_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage number
book_idYesBook ID
languageNoSummary language (default: Arabic)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description is doing the heavy lifting by disclosing that summarization runs on the client's model via sampling rather than server-side. That is meaningful behavioral context (latency, model dependency, failure if the client lacks sampling), but it omits what happens on sampling failure and what the returned summary looks like.

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 short sentences, zero waste, with the core action front-loaded and the prerequisite immediately following. Nothing here could be cut without losing information.

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 only three simple parameters and no output schema, the definition covers the essentials but leaves the return contract and error path unstated — notable for a tool whose whole behavior hinges on an optional client capability. An agent knows what it does and what it needs, but not what it gets back or what happens when sampling is unsupported.

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%, with page, book_id, and language all documented including the Arabic default, so the baseline of 3 applies. The description adds no parameter meaning beyond the schema, such as page-range bounds or language fallback rules.

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?

Names a specific verb (summarize) and resource (a book page) and, crucially, explains the mechanism: it fetches the page and delegates summarization to the client's own model. That clearly separates it from plain retrieval siblings like turath_get_page, though the description never names that sibling explicitly.

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 states a hard prerequisite ('Requires a client with sampling support'), which is a real usage condition an agent must check before calling. However, it gives no guidance on when to prefer this over fetching a page and summarizing yourself, nor any exclusions or fallback behavior when sampling is unavailable.

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