Skip to main content
Glama
Sign In
co-reading-mcp

co-reading-mcp

by kikuovo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Read reading notes

read_notes

Retrieve discussion notes for a book to restore context between sessions without re-reading.

Instructions

Read the accumulated discussion notes for a book, used to restore context cheaply between sessions.

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": {
      "bookId": "<bookId>"
    },
    "name": "read_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries full burden. It mentions 'cheaply' hinting at low cost, but does not disclose read-only nature, authentication needs, or return format.

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?

Single 16-word sentence with clear front-loading ('Read the accumulated discussion notes for a book') and an additional usage hint; no wasted words.

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?

Tool is simple with one parameter and no output schema; description omits what is returned (notes text, format, structure), reducing completeness for an agent.

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 has 0% description coverage and the description does not explain the bookId parameter or how to obtain it, leaving the agent to infer meaning from the name alone.

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?

Description clearly states it reads accumulated discussion notes for a book, distinguishing it from sibling tools like append_notes (which adds notes) and list_annotations (lists annotations). Verb and resource are specific.

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?

Description provides a use case ('restore context cheaply between sessions'), implying lightweight retrieval, but lacks explicit when-not-to-use or alternative recommendations.

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