Skip to main content
Glama

ReadingRate

Get passages near the reader's position

get_passages_near_reading_position
Read-onlyIdempotent

Returns passages of text from a book the reader is reading, taken from the pages just before their current position in ReadingRate, with their progress in the book. It finds the book and the page itself, so the reader does not have to name the chapter. With a topic, it returns the passages near their position that are closest to that topic.

Use when the reader asks for help with what they just read: the last chapter, a passage they did not understand, or what the author meant in the part they have reached. To search a whole book for a topic, use search_book_content.

Text is available only for books the reader uploaded their own copy of in the ReadingRate app. For other books the result says the text is not available; the book's scores and analysis are in get_book_details.

Examples:

  • {}

  • {"book_id": "", "topic": "the argument about metempsychosis"}

Input Schema

NameRequiredDescriptionDefault
topicNoWhat the reader wants help with, e.g. "narrative voice"; focuses the passages returned
book_idNoThe book: its ReadingRate id or library entry id (default: the book the reader read most recently)

Output Schema

NameRequiredDescriptionDefault
bookYesThe book and the user's reading position
noteYesGuidance on how to use the passages (or why none were found)
passagesYesText passages from near the user's reading position
passages_foundYesNumber of passages returned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior. The description adds meaningful non-obvious context: text availability is limited to books the reader uploaded, and unavailable text is reported in the result with book analysis routed to get_book_details.

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?

Front-loaded with what it returns, then usage guidance, then availability constraints and examples. It is somewhat verbose, but the structure is clear and each paragraph serves a distinct purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for an agent: it covers retrieval scope, automatic position detection, topical filtering, when to use it versus a sibling, data availability limits, and fallback behavior. An output schema exists, so return-value detail is not required.

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 both parameters are already documented in the schema. The description adds useful framing about automatic book/page discovery and topical focusing, but does not add format or edge-case detail beyond the schema.

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: returns text passages near the reader's current position in ReadingRate. It also distinguishes itself from search_book_content and get_book_details by explaining what it does versus those siblings.

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

Usage Guidelines5/5

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

Explicitly says when to use it: when the reader asks about what they just read, a recent passage they did not understand, or the part they have reached. It also names the alternative, search_book_content, for whole-book topical search.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.