Skip to main content
Glama

update_read_progress

Set a bookmark's reading progress from 0.0 to 1.0 to track where you left off in long articles or research papers.

Instructions

Track reading progress on a bookmark. Provide a progress value between 0.0 (not started) and 1.0 (finished). Useful for tracking where you left off in long articles or research papers.

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": {
      "bookmark_id": "<bookmark_id>",
      "progress": "<progress>"
    },
    "name": "update_read_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
progressYesReading progress as a decimal (0.0 = not started, 1.0 = finished)
bookmark_idYesID of the bookmark

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/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 behavioral burden. It implies a mutation but does not state whether existing progress is overwritten, whether ownership or permissions are required, or what side effects occur. Only the progress range is explained, which is already schema-level detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, but it repeats the progress range already present in the schema and includes a somewhat tangential 'useful for' sentence. Every sentence is not fully earning its place.

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?

This is a two-parameter mutation tool with no annotations and no output schema, so the description should disclose mutation semantics, permission needs, and how it relates to the bulk variant. It instead focuses on progress-range explanation and a use-case example, leaving important behavioral context unaddressed.

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 100%, so the baseline is 3. The description repeats the 0.0–1.0 progress range and bookmark target but adds no meaning beyond what the schema already documents.

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 uses a specific verb and resource: 'Track reading progress on a bookmark.' The singular 'a bookmark' implicitly differentiates it from the bulk sibling update_read_progress_bulk, though that distinction is not made explicit.

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?

It gives a contextual use case ('long articles or research papers') but does not state when to use this tool versus update_read_progress_bulk or what prerequisites exist. Usage is implied rather than explicitly guided.

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