Skip to main content
Glama

Coline

Mark read

mark_conversation_read
Idempotent

Marks a conversation read (up to a message, or all of it) or unread (all of it, or from a message on) for the person.

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": {
      "workspace": "<workspace>",
      "type": "<type>",
      "conversationId": "<conversationId>"
    },
    "name": "mark_conversation_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYes
stateNoThe whole conversation.
messageIdNoRead up to here.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
conversationIdYesChannel or direct message id, from list_conversations.
unreadFromMessageIdNoUnread from here on.

Output Schema

NameRequiredDescriptionDefault
okYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=false, idempotent=true, destructive=false and openWorld=false, so the safety profile is largely covered. The description adds one genuinely useful behavioral fact — the change applies 'for the person', i.e. only the caller's read state, not everyone's — but says nothing about unread-count/notification side effects or what happens if messageId is passed with an incompatible state.

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 front-loaded sentence with no filler; the parenthetical scoping is dense but readable. Slightly compact to the point of ambiguity about parameter coupling, but nothing is wasted.

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?

With annotations, a full input schema at high coverage, and an output schema present, the description only needs to explain the read/unread scope model, which it does. The remaining gap is the missing routing versus read_conversation and the validity rules for combining state with message parameters.

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 83% and the per-field descriptions ('The whole conversation', 'Read up to here', 'Unread from here on') already carry most of the meaning. The description restates those in prose and hints at the state/message pairing, but does not explicitly say which parameter is valid for which state, which is the one thing the schema leaves implicit.

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?

States a specific verb and resource ('Marks a conversation read ... or unread') and precisely enumerates the scope variants (up to a message, all of it, from a message on). This implicitly separates it from the read_conversation sibling, but it never names or contrasts any alternative explicitly.

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?

Usage is only implied: an agent can infer this is the tool for changing read state rather than reading content, but there is no statement of when to prefer it, no prerequisites, and no guidance on invalid state/message combinations.

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