co-reading-mcp

Set reading progress

set_progress

Define the reading position in a book by specifying the book ID and the chunk ID to jump to or resume from.

Instructions

Manually set the last-read chunk id for a book (e.g. to jump or re-read).

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

Input Schema

Name	Required	Description	Default
`bookId`	Yes
`chunkId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

A4/5.0

Behavior3/5

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

The description states it's a manual set operation, indicating mutation, but doesn't disclose potential side effects, validation, or authorization needs. With no annotations providing safety cues, this is minimally transparent.

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 sentence of 14 words, front-loaded with the action, and efficient with zero waste. Every word earns its place.

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?

For a simple tool with two required string params and no output schema, the description adequately covers purpose and one use case. It doesn't discuss return values or error handling, but complexity is low, so it's mostly 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 description coverage is 0%, so the description must compensate. It implicitly maps 'book' to bookId and 'last-read chunk id' to chunkId, but adds no extra detail like format or constraints, providing only baseline semantic context.

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 the verb 'set', the resource 'last-read chunk id for a book', and provides an example use case ('to jump or re-read'), which distinguishes it from siblings like 'get_progress' and 'read_chunk'.

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

Usage Guidelines4/5

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

The description implies usage with the example 'to jump or re-read', offering clear context. However, it lacks explicit exclusions or prerequisites (e.g., book must exist, chunk must be valid), which would strengthen guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server