Skip to main content
Glama

mark_read

DestructiveIdempotent

Marks every page of a Kavita series as read, replacing the current reading position so you can complete a title in one action.

Instructions

Mark every page of the book as read (replaces the current position).

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": {
      "series_id": "<series_id>"
    },
    "name": "mark_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
series_idYesKavita series ID (from list_library, search or add_document)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description earns credit for adding the concrete consequence beyond the annotations: the existing reading position is replaced, which tells the agent exactly what is destroyed and that re-invoking is harmless because everything ends up read anyway.

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?

One short sentence plus a parenthetical, both front-loaded and free of filler. The destructive consequence sits directly next to the action it qualifies.

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 one-parameter mutation tool the description covers what changes, that it is exhaustive, and that prior position is lost, while annotations and a fully documented schema cover safety and ID sourcing. The only gap is the unresolved book-versus-series wording, which slightly muddies what entity the ID refers to.

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% for the single series_id parameter, including a description pointing to list_library, search, and add_document as sources of the ID, so the schema does the heavy lifting. The description adds nothing about the parameter and notably says "book" while the parameter is series_id, a slight terminology mismatch.

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 gives a specific verb and resource ("mark every page of the book as read") and adds a scope qualifier ("every page"), so the agent knows this is a bulk state change rather than a partial one. It does not name any sibling such as reading_status or want_to_read to distinguish it from adjacent status tools, so it falls short of a 5.

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?

Usage is only implied: the parenthetical about replacing the current position hints at what happens when a book is already partially read, but there is no explicit when-to-use guidance, no mention of the inverse operation (unmarking), and no pointer to reading_status for checking or adjusting state.

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