Skip to main content
Glama

Library of Alexandria

by io.github.ltvspot
OverviewDiscussionsAdmin

Get a chapter summary

get_chapter_summary
Read-onlyIdempotent

Get the summary of one chapter, act or section of a title, or, without a number, the list of its chapters with their titles. Each summary is a few hundred words at most and points to the next one. A title whose chapter summaries are not open yet says that they open here soon.

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.
chapterNoNumber of the chapter, act or section, starting at 1. Leave it out to get the list of chapters.
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.

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.7/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description's added value is notable: it discloses summary length ('a few hundred words at most'), the chaining behavior ('points to the next one'), and the availability/lock state message for unopened summaries. That last detail is real behavioral context an agent would not otherwise know.

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?

Compact and front-loaded: the primary mode is stated first, followed by the list mode, then two short caveats about length and availability. No wasted sentences.

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?

With no output schema, the description carries the burden of explaining returns and does so reasonably: it characterizes the summary content, the chapter-list shape, and the not-yet-open state. Minor gaps remain around how the 'points to the next one' reference is expressed, but the essentials are covered.

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%, including the enum languages and the note that omitting chapter returns the list, so the schema does the heavy lifting. The description restates the chapter-omission behavior but adds no format or syntax detail beyond the schema.

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 the summary of one chapter, act or section') and clearly covers the dual mode of returning either a summary or a chapter list. It does not, however, distinguish itself from related siblings like get_summary or get_book_outline, so an agent must infer the granularity difference.

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?

The 'without a number, the list of its chapters' clause gives implicit guidance on when to omit the chapter parameter, but there is no explicit statement of when to prefer this tool over get_summary or get_book_outline. Usage context is implied rather than stated.

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