Skip to main content
Glama

Library of Alexandria

by io.github.ltvspot
OverviewDiscussionsAdmin

Open in reader

open_in_reader
Read-onlyIdempotent

Get a chapter address for the signed-in member to open in the reader. Only open titles are linked, and the reader checks chapter access.

Input Schema

NameRequiredDescriptionDefault
idYesTitle id as found in a search result, for example top3500-00013 or forbidden-00004. A plain number is read as a number of the main list.
chapterNoChapter number, default 1.
languageNoLanguage of the person asking, as a code: en English, es Spanish, de German, nl Dutch, fr French, it Italian, pt-BR Portuguese, ru Russian, zh-CN Chinese, zh-TW Chinese in traditional characters, ja Japanese, ko Korean, pl Polish, ar Arabic, hi Hindi, id Indonesian, ca Catalan. Titles, subtitles, authors and page addresses come back in this language. Default: the language of the query, else English.
paragraphNoOptional paragraph id such as p3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / language / description
      Previous value: -"Language of the person asking, as a code: en English, es Spanish, de German, nl Dutch, fr French, it Italian, pt-BR Portuguese, ru Russian, zh-CN Chinese, zh-TW Chinese in traditional characters, ja Japanese, ko Korean, pl Polish, ar Arabic, hi Hindi, id Indonesian. Titles, subtitles, authors and page addresses come back in this language. Default: the language of the query, else English."New value: +"Language of the person asking, as a code: en English, es Spanish, de German, nl Dutch, fr French, it Italian, pt-BR Portuguese, ru Russian, zh-CN Chinese, zh-TW Chinese in traditional characters, ja Japanese, ko Korean, pl Polish, ar Arabic, hi Hindi, id Indonesian, ca Catalan. Titles, subtitles, authors and page addresses come back in this language. Default: the language of the query, else English."
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "en",
-  "es",
-  "de",
-  "nl",
-  "fr",
-  "it",
-  "pt-BR",
-  "ru",
-  "zh-CN",
-  "zh-TW",
-  "ja",
-  "ko",
-  "pl",
-  "ar",
-  "hi",
-  "id"
-]New value: +[
+  "en",
+  "es",
+  "de",
+  "nl",
+  "fr",
+  "it",
+  "pt-BR",
+  "ru",
+  "zh-CN",
+  "zh-TW",
+  "ja",
+  "ko",
+  "pl",
+  "ar",
+  "hi",
+  "id",
+  "ca"
+]
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior. The description adds meaningful context beyond that: the caller must be a signed-in member, only open titles are linked, and chapter access is checked by the reader itself. It stops short of describing error behavior for closed titles or expired access, so it is strong but not exhaustive.

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 sentences, both front-loaded with the essential operation and the key access constraint. There is no repetition of schema or annotation content and no unnecessary preamble.

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?

For a low-complexity read tool with full schema coverage and annotations covering safety, the description supplies the crucial auth and access constraints. Without an output schema, a brief note on the address format or failure behavior for unlinked titles would complete it, but it is otherwise adequate.

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 the schema already defines id, chapter, language, and paragraph in detail. The description adds no parameter-specific meaning, so the baseline score of 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?

States a specific verb and resource: 'Get a chapter address ... to open in the reader', scoped to the signed-in member. It is clearly not a full book fetch or a free-chapter read, though it does not name sibling alternatives like read_free_chapter or get_book 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?

Usage is implied by 'to open in the reader' and the signed-in member constraint, but there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative such as read_free_chapter for free chapter reading.

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

All Library of Alexandria toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources