Skip to main content
Glama

Mark Conversation Read

mark_conversation_read
Idempotent

Mark a single Canvas Inbox conversation as read to clear its unread status without notifying the sender; use the unread action to reverse it.

Instructions

Mark one Inbox conversation as read. Only affects you; the sender is not notified. Reverse with mark_conversation_unread.

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "mark_conversation_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversation_idYesInbox conversation ID (numeric string). Get it from list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / conversation_id / description
      Previous value: -"Canvas ID (numeric string)"New value: +"Inbox conversation ID (numeric string). Get it from list_conversations."
  2. First observedv1.0.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive mutation. The description goes beyond them by disclosing effect scope ('Only affects you; the sender is not notified') and reversibility via a named sibling, which is genuine behavioral context an agent would otherwise have to guess. It does not cover failure modes or permission requirements, keeping it below a 5.

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, front-loaded with the action and scope, followed by side-effect and reversibility notes. Every clause earns its place with no filler.

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 simple one-parameter state toggle with full annotation coverage and a fully described schema, the description supplies everything an agent needs: what changes, whose state changes, no notification side effect, and how to undo it.

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?

With a single parameter at 100% schema description coverage, the schema already documents conversation_id and even its source (list_conversations). The description adds no format, constraint, or sourcing detail beyond that, so the baseline 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 one Inbox conversation as read') with explicit scope ('one Inbox conversation'), and immediately names the inverse sibling mark_conversation_unread. An agent can distinguish this from unread toggling and batch operations without opening the schema.

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?

The description makes the use case clear (reading state of a single conversation) and explicitly points to mark_conversation_unread as the reverse action, giving concrete sibling routing. It stops short of stating exclusions such as when to use batch_update_conversations or mark_all_* variants instead.

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

Deploy Server

Other Tools