Skip to main content
Glama

want_to_read

DestructiveIdempotent

Add or remove a Kavita series from your read-next queue so it appears in Kavita and on your e-reader over OPDS.

Instructions

The user's "read next" queue, shown in Kavita and over OPDS on the e-reader.

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": "want_to_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionNoadd or removeadd
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

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=true, so safety is partly covered. The description adds only that the queue is visible in Kavita and on the e-reader via OPDS, and says nothing about the removal path being destructive or how these entries relate to reading status.

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

Conciseness4/5

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

A single short sentence with zero filler, front-loaded on the resource. It is lean to the point of under-specification, but nothing is redundant or buried.

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?

For a destructive mutation tool, the description omits the add/remove duality, the default of action=add, and any effect on the reading pipeline. Annotations cover the safety profile, but the definition still leaves an agent to reconstruct the tool's actual behavior from the title and schema.

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%: both action (enum add/remove, default add) and series_id (sourced from list_library, search, or add_document) are documented in the schema. The description adds no parameter meaning, so baseline 3 applies.

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

Purpose3/5

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

The description names the resource (the user's "read next" queue) and where it surfaces, but never states the operation the tool performs. 'Add to or remove from' appears only in the annotation title and the schema enum, so an agent reading the description alone learns what the queue is, not what the tool does to it.

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?

There is no when-to-use guidance, no exclusion, and no pointer to alternatives such as mark_read or reading_status, which an agent might plausibly confuse with queue management. The Kavita/OPDS mention is descriptive context, not usage direction.

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