Skip to main content
Glama
Sign In
Digital Life Library MCP Server

Digital Life Library MCP Server

by August-lky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

shelf_read

Continue reading a book from where you left off, automatically saving progress after each segment and allowing a restart from the beginning.

Instructions

接着上次读到的地方往下读一段（停在段落结尾）。读到哪会自动记住。想从头读可以 restart。

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

Input Schema

NameRequiredDescriptionDefault
bookYes书名或书 id
charsNo这一段大概多少字，默认 1500
restartNo
togetherNo和别人一起读：几个人共用同一份进度（谁读都往下走）

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key side effect: progress is automatically persisted ('读到哪会自动记住') and restart resets it. It stops short of saying what happens at the end of the book, whether the position is shared across sessions, or what errors occur for an unknown book.

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?

Three short sentences, zero filler, and the core behavior (resume from last position, stop at paragraph end) is front-loaded ahead of the optional restart escape hatch.

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

Completeness3/5

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

There is no output schema and no annotations, so the description should hint at what a read returns (the text segment itself?) and what happens when the book is exhausted. It covers the resume/persist mechanic well but leaves return value and edge cases unstated.

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 coverage is 75% and the one undocumented parameter, restart, is explained in the description ('想从头读可以 restart'), which is real added value. 'chars' is only implied via '一段' / '停在段落结尾' and the 1500 default is left entirely to 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 ('接着上次读到的地方往下读一段'), plus the scope of one read (stops at paragraph end). It is clearly the reading tool among siblings like shelf_status, shelf_bookmark and shelf_list, though it never names a sibling to contrast with.

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 rather than stated: continue from the saved position, or set restart to begin at the start. There is no explicit when-to-use / when-not-to-use guidance and no routing to alternatives such as shelf_status for checking position instead of reading.

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