Skip to main content
Glama

Mark the chat as read

chat_mark_read
Idempotent

Marks chat as read up to a specific message, reducing the signed-in member's unread count and updating the visible read position; older message IDs are ignored.

Instructions

Records that the signed-in member has read the chat up to a message, which lowers the chat_unread count and updates the read position other members see in chat_messages. The marker only moves forward: an older message id is ignored, and the response says whether the marker moved. An id that is not in this flat gives message_not_found. Use this after reading with chat_messages; it does not read or send anything.

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

Input Schema

NameRequiredDescriptionDefault
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
lastReadMessageIdNoId of the newest message the member has read, from chat_messages. Send null or omit it to reset the marker.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / lastReadMessageId / description
      Added value: +"Id of the newest message the member has read, from chat_messages. Send null or omit it to reset the marker."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), the description discloses the monotonic marker rule (older ids ignored), that the response reports whether the marker moved, and the message_not_found error for ids outside this flat. This is exactly the write-behavior context the annotations cannot convey.

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 dense sentences with no filler: effect and counting consequence first, then the forward-only rule and error case, then the usage note. Everything is front-loaded and each sentence carries distinct information.

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 write tool with no output schema, the description covers side effects, constraint behavior, failure mode, and the meaning of the response (whether the marker moved). Nothing an agent needs to call it correctly or interpret the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3, but the description adds real semantics: lastReadMessageId's monotonic constraint (older ids ignored) and the "this flat" scoping that explains wgCode. It stops short of describing the null-reset behavior, which only the schema carries.

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 ("Records that the signed-in member has read the chat up to a message") plus the observable effects on chat_unread and the read position in chat_messages. It also pre-empts confusion with chat_messages and chat_send by stating "it does not read or send anything."

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?

"Use this after reading with chat_messages" gives explicit ordering and names the sibling that precedes it. There is no explicit when-not/exclusion guidance, but the clarification that it does not read or send anything covers the most likely misuse.

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