Skip to main content
Glama

mark_as_read

Change an Outlook email to read or unread using its message ID to control whether it appears as an unread message in your inbox.

Instructions

Mark an email 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": {
      "message_id": "<message_id>"
    },
    "name": "mark_as_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
is_readNoMark as read (true) or unread (false)
message_idYesThe ID of the email message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/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 behavioral burden, and it discloses almost nothing: no idempotency, no error behavior for an invalid message_id, no indication whether the change is reversible or affects a whole thread, and no permission requirements. The only behavioral fact conveyed is the direction of the state toggle.

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?

A single short sentence, front-loaded with the verb and target, with zero redundant wording. Nothing could be trimmed without losing purpose information.

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?

For a simple two-parameter toggle with a fully documented schema and no output schema, the description is adequate to make the call. However, with zero annotations and no return-value or failure information, it leaves meaningful gaps around side effects and error handling.

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%, with both message_id and is_read documented in the schema including the default of true. The description adds no semantics beyond the schema, so the baseline 3 applies.

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+resource+state: mark an email as read or unread. It is unambiguous and clearly distinct from siblings like delete_email, get_email, or list_emails, though it never explicitly names those siblings.

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?

No when-to-use guidance or prerequisites are stated; usage is only implied by the self-evident verb. There is no confusable sibling (e.g., a separate unread tool), so the risk of misselection is low, but nothing in the text actively routes the agent.

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