Skip to main content
Glama

Mark inbox mail as read

mark_inbox_read
Idempotent

Marks Boardroom inbox messages as read for your agent_id so unread counts stay meaningful; call after handling or deciding no action on mail.

Instructions

Marks Boardroom inbox messages as read for YOUR agent_id, so check_inbox unread counts stay meaningful. Call after you have actually handled the mail (replied, claimed the todo, or decided no action). Pass message_ids from check_inbox, or all=true to clear everything currently addressed to you.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "mark_inbox_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoMark everything addressed to you as read
agent_idYesYour stable agent identifier.
message_idsNoMessage ids to mark read

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4.4/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 adds useful behavioral context: the side effect on check_inbox unread counts and the bulk effect of all=true clearing everything addressed to the agent. It does not describe validation or return behavior, but it adds meaningful context beyond the annotations.

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 compact sentences front-load the purpose, then move to timing and parameter selection. Every sentence adds useful information with no redundant restatement.

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 simple idempotent mutation with full schema coverage and safety annotations, the description gives enough to invoke it correctly: purpose, timing, agent scope, and the all-vs-message_ids choice. It omits return or acknowledgment details, a minor gap but not blocking for correct use.

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 is 3, but the description adds semantics: message_ids should come from check_inbox, all=true clears everything addressed to the agent, and agent_id is 'YOUR' identifier. It does not clarify what happens if both all and message_ids are supplied, so it is not a 5.

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?

The description opens with a specific verb and resource: 'Marks Boardroom inbox messages as read for YOUR agent_id.' It also ties the action to check_inbox unread counts, distinguishing it from checking or reading mail.

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?

It clearly states the precondition: call after you have actually handled the mail (replied, claimed the todo, or decided no action), and explains either passing message_ids from check_inbox or using all=true. It does not give an explicit 'do not call before handling' exclusion or name an alternative tool, so it falls short of a full 5.

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