Lion Reader

mark_entries_read

Idempotent

Mark up to 1000 entries as read or unread in one call. Reversible (call again with the opposite read) and idempotent. Returns the entries' new state (IDs the user can't see are left out) and, when anything changed, the affected unread counts. To star an entry use star_entries.

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": {
      "entryIds": "<entryIds>",
      "read": "<read>"
    },
    "name": "mark_entries_read"
  }
}

Input Schema

Name	Required	Description	Default
`read`	Yes	Mark as read (true) or unread (false)
`entryIds`	Yes	Array of entry IDs to mark

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the description adds real value on top: it discloses that the call returns each entry's new state, that entries invisible to the user are silently omitted, and that unread counts are returned only when something changed. It does not address permission requirements or partial-failure behavior for invalid IDs.

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?

Three short sentences, zero padding, with the operation and its batch limit front-loaded and the sibling pointer at the end. Every clause carries information an agent would otherwise have to infer.

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

Completeness5/5

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

For a two-parameter mutation with no output schema, the description supplies the return shape, the invisible-entry exclusion, and the conditional unread-count payload. Nothing material is missing for correct invocation.

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%, with both `read` and `entryIds` documented inline, including the maxItems of 1000. The description's "up to 1000" restates the schema rather than adding new meaning, so the baseline of 3 applies.

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?

States a specific verb and resource ("Mark ... entries as read or unread") plus the batch ceiling of 1000 in one call. It is immediately distinguishable from siblings like star_entries, which the description explicitly points to.

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?

Gives the key routing cue for the nearest ambiguous case ("To star an entry use star_entries") and clarifies that the operation is reversible by calling again with the opposite `read`. It stops short of stating when not to use it, e.g. bulk operations beyond 1000 entries or per-subscription marking.

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

All Lion Reader tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.