Skip to main content
Glama

Mark a conversation read

thread_mark_read
Idempotent

Marks messages in one of your conversations as read up to up_to_seq (default: all). Reading with thread_get never does this on its own, so only call it when the human has actually seen the messages.

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": {
      "thread": "<thread>"
    },
    "name": "thread_mark_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadYesConversation reference (TH-…) from threads_list.
up_to_seqNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context that thread_get does not mark read and that this is a human-acknowledgement action, but it says nothing about the effect on unread counts, whether it can be undone, or what is returned.

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?

Two tight sentences, front-loaded with the action and its default, followed by the usage constraint. No redundant restatement of the title or annotations.

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

Completeness4/5

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

For a two-parameter, non-destructive, idempotent mutation with no output schema, the description covers purpose, default behavior and the critical usage condition. Only the provenance of up_to_seq values is left implicit.

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 50%: thread is documented in the schema, but up_to_seq has no schema description. The description compensates by explaining that it marks read up to that sequence and defaults to all, which is the key semantic an agent needs. It does not say where a valid sequence value comes from, leaving a small gap.

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 (marks as read) and resource (messages in a conversation), plus the scoping parameter up_to_seq with its default. It explicitly distinguishes itself from thread_get, so an agent can tell the two apart without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use rule: only call when the human has actually seen the messages. It also names the tempting alternative (thread_get) and clarifies that reading does not implicitly mark read, which is exactly the confusion an agent would otherwise have.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources