Skip to main content
Glama
Sign In
librarian

librarian

by Terobyte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

list_chapters

Retrieve a book's table of contents by ID, including chapter number, title, token count, and summary for each chapter.

Instructions

Table of contents for a book by its id: chapter number, title, token count, and a short summary for each chapter.

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>"
    },
    "name": "list_chapters"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the transparency burden. It discloses the output fields (chapter number, title, token count, summary) which is useful, but does not mention permissions, limitations, or any side-effect behavior. This is adequate but not comprehensive for a tool with zero annotation support.

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?

The description is a single, concise sentence that front-loads the tool's purpose and output. Every word contributes to understanding, with no fluff or redundancy.

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?

Given the tool has only one parameter and an output schema exists, the description sufficiently covers the essential behavior. It lacks usage alternatives and edge-case details, but for a straightforward list operation, it is largely complete.

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?

The schema has 0% description coverage, so the description's phrase 'by its id' adds minimal semantic meaning to book_id, clarifying it is the book identifier. However, it does not explain the id format or any constraints, leaving the parameter only slightly enhanced over the raw 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?

The description clearly identifies the tool as providing a table of contents for a book by its id, listing chapter number, title, token count, and summary. This distinguishes it from list_books and book_info, though it does not explicitly contrast with the similarly named get_chapters sibling.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives like get_chapters. The description merely states what it does, leaving the agent to infer usage context without any exclusions or preference rules.

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