Skip to main content
Glama
Sign In
mcp-server-weread

mcp-server-weread

by ChenyqThu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_book_notes_and_highlights

Retrieve all notes and highlights from a book, organized by chapter for easy review.

Instructions

Get all highlights and notes for a specific book, organized by 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": "get_book_notes_and_highlights"
  }
}

Input Schema

NameRequiredDescriptionDefault
book_idYesBook ID
include_chaptersNoWhether to include chapter information
organize_by_chapterNoWhether to organize by chapter
highlight_styleNoHighlight style filter, null means all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only describes the basic function and output organization, lacking details on permissions, side effects, error handling, or limits.

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 of 12 words, front-loading the key action and resource. No unnecessary or redundant information.

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?

Given the absence of an output schema, the description partially explains the structure ('organized by chapter') but omits details on returned fields, pagination, or error handling. Adequate but not fully 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?

Schema coverage is 100% with parameter descriptions. The description adds no new semantic value beyond the schema, but it does reinforce the 'organize_by_chapter' parameter. Baseline for high coverage is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Get all highlights and notes for a specific book, organized by chapter', specifying verb, resource, scope, and organization. It distinctly differs from sibling tools like get_book_best_reviews, get_bookshelf, and search_books.

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?

The description does not provide any guidance on when to use this tool versus alternatives, nor does it mention when not to use it. Implicit differentiation from siblings is not enough.

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