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_bookmark

Save your current reading position with a bookmark and add a personal note. Track progress on your local bookshelf.

Instructions

在现在读到的位置夹一个书签，可以写一句自己的感想。

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_bookmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookYes
noteNo
togetherNo夹在「一起读」的进度上

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden and does not meet it. It does not say whether a reading session/position must already exist, whether an existing bookmark is replaced, whether the note is optional, or what the tool returns on success.

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?

A single compact sentence that front-loads the core action with no filler. It is appropriately sized for a one-liner but borders on under-specification for a mutation tool with three parameters.

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

Completeness2/5

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

A mutation tool with no annotations, no output schema, and a third of its parameters undocumented in both schema and description. The agent lacks prerequisites, side effects, and return expectations, all of which the description would need to supply here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%: 'together' is documented in the schema, while 'book' and 'note' are bare strings. The description clarifies 'note' as a personal reflection but says nothing about what 'book' identifies (title, ID, path?) or how it relates to the current reading position.

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 states a concrete verb and object – placing a bookmark at the current reading position – which an agent can distinguish from container tools such as library_browse or shelf_list. It never names the closest siblings (library_mark, library_save), so discrimination relies on inference.

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 phrase 'at the current reading position' implies when the tool applies, but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives like library_mark. The agent must guess the relationship between bookmarking and marking.

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