Skip to main content
Glama

mark_chat_read

Idempotent

Marks every message in a chat as read and clears its unread badge, so agents can keep chat status current after reviewing conversations.

Instructions

Mark every message in a chat as read (clears its unread badge).

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": {
      "chat": "<chat>"
    },
    "name": "mark_chat_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered. The description adds real value by naming the observable effect (unread badge cleared) and the bulk scope, but says nothing about whose read state is affected, whether read receipts become visible to other chat members, or what happens if messages arrive mid-operation.

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 sentence, front-loaded with the action and scope, with the parenthetical delivering the only extra fact an agent needs. Nothing is redundant.

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?

For a simple one-parameter mutation with an output schema and four annotations, the description covers the action and its visible effect and needs no return-value explanation. The gaps that remain—permission requirements, identifier format, and cross-user effects—are exactly the parts a caller would want before invoking a state-changing tool.

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 0% on a single required parameter, so the description must carry the meaning and it only implies "a chat" maps to the chat argument. It does not specify whether the value is an ID, a workspace-qualified ID, or a name, leaving format ambiguity.

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?

"Mark every message in a chat as read" gives a specific verb plus resource and scope (all messages, not one), which cleanly separates it from read_chat and get_project_chat. No sibling is named explicitly, so it stops 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?

The parenthetical "clears its unread badge" implies the situation in which the tool is used, but there is no explicit when-to-use statement, no prerequisites, and no named alternative for marking a single message read.

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