Skip to main content
Glama

reading_status

Read-onlyIdempotent

Track reading progress: view books currently in progress, titles not yet started, or your want-to-read queue, to answer what you're in the middle of and what's next.

Instructions

Answers "what am I in the middle of?", "what haven't I read?" and "what's next?".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "reading_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewNoon_deck: in progress; unread: not started; want_to_read: the queueon_deck
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context of its own: no indication of what is returned, how results are ordered, or how limit interacts with the views.

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 no filler, and the three phrasings are compact and readable. It is slightly redundant since all three questions point at the same retrieve-reading-state operation, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple, two-parameter read tool with annotations and no output schema, so moderate coverage suffices. Still, the description never says what comes back (a document list?) or how limit affects the result, which an agent would need since no output schema exists to explain it.

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 50%: view is well documented in the schema, limit is not. The three questions loosely gloss the view semantics but largely restate what the enum description already says, and limit (including its cap of 100) is never addressed.

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 three questions ("what am I in the middle of?", "what haven't I read?", "what's next?") map onto the three view values, so an agent can infer this returns the user's reading queue state. However, there is no verb+resource statement such as "list documents by reading status", and nothing distinguishes it from siblings like want_to_read or list_library.

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?

The question framing implies when each view is appropriate (in-progress vs. not-started vs. queue), which is useful implied guidance. But there is no explicit statement of when to call this tool instead of want_to_read, list_library, or search, and no mention of prerequisites.

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