Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

mark_message

Set an Outlook email as read or unread by message ID to keep inbox status accurate and organized.

Instructions

Mark a Message as read or 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": {
      "messageId": "<messageId>",
      "isRead": "<isRead>"
    },
    "name": "mark_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
isReadYestrue to mark as read, false to mark as unread
messageIdYesThe Message ID to mark

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It says nothing about permissions needed, whether the change is idempotent, whether unread state is restored, or whether the operation touches only the current user's copy. Marking read state is a mutation and that behavior is undisclosed.

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 short sentence with no filler, and the core action is front-loaded. It is arguably too terse for a mutation tool, but not wasteful.

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?

This is a simple two-parameter, flat-schema tool with no output schema, so little explanation is strictly required. Still, a mutation with no annotations would benefit from a note on scope (whose message) and whether re-marking is harmless.

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 description coverage is 100%: isRead is documented as a boolean toggling read/unread and messageId as the target ID. The description adds no extra meaning beyond those field descriptions, which is the baseline expectation when the schema is fully documented.

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?

The description gives a specific verb (mark) and resource (Message) plus the two target states (read/unread). That clearly distinguishes it from siblings like get_message, delete_message, and forward_message, though it doesn't name any of them explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no note about prerequisites such as the message already being in the mailbox, and no mention of alternatives. The intent of the tool is only implied by the verb.

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