Skip to main content
Glama

read_pages

Read specific pages (e.g. "3,7,9-11") or a heading from the outline of a document already opened with read_document. Retrieves only the pages you need instead of the full file.

Instructions

Read specific pages of a document already opened with read_document. Pass pages (e.g. "3,7,9-11") or section (a heading from the outline), not both. Free: never charges.

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": {
      "document_id": "<document_id>"
    },
    "name": "read_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pagesNo
sectionNo
document_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden; it discloses the non-obvious prerequisite (document must already be opened) and the cost behavior ('Free: never charges'), which an agent could not infer. It omits failure behavior for an invalid range or a heading not in the outline, so coverage is strong but not complete.

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 tight sentences with zero filler; the prerequisite and the required input choice come first and the cost note last, all earning their place.

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?

An output schema exists, so return values need not be explained, and the description covers prerequisite, input formats and mutual exclusion for a three-parameter read tool. Minor gaps remain around invalid-input and not-found behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it does: it supplies the page-range syntax ('3,7,9-11'), defines section as 'a heading from the outline' and states the mutual exclusivity of the two. Only document_id is left undefined, which prevents a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read specific pages of a document') and immediately ties it to the sibling prerequisite 'already opened with read_document', so the agent can distinguish it from read_document and export_table without opening a schema.

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

Usage Guidelines4/5

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

Gives clear context (must first use read_document) and an explicit exclusion rule ('Pass pages ... or section ..., not both'). It does not explicitly say when to fall back to read_document for a whole document, so it stops short of full when/when-not coverage.

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

Deploy Server

Other Tools