Skip to main content
Glama

graph_flag_mail

Sets follow-up flags on up to 50 Outlook messages at once, choosing notFlagged, flagged, or complete and optionally targeting a shared mailbox. Reports per-message outcomes.

Instructions

Set the follow-up flag on messages.

Processes each message in order and reports per-message outcomes.

Args: message_ids: Message IDs to update (1-50 per call). flag_status: Flag state: "notFlagged", "flagged", or "complete" (default "flagged"). mailbox: Shared mailbox address or user ID to act on. Empty targets your own mailbox. Requires the delegated Mail.*.Shared permissions.

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_ids": "<message_ids>"
    },
    "name": "graph_flag_mail"
  }
}

Input Schema

NameRequiredDescriptionDefault
mailboxNo
flag_statusNoflagged
message_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A4.7/5.0
Behavior5/5

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

Since no annotations were provided, the description carries the full burden. It clearly discloses that the tool processes messages sequentially and reports outcomes, along with a crucial requirement: delegated Mail.*.Shared permissions.

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?

The definition is well-structured, with the purpose at the top and parameter details logically grouped. It is highly efficient, using a short block of text to explain the core functionality and constraints.

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?

The definition is highly complete for a mutation operation with only three parameters and no defined output schema. It covers prerequisites (permissions), operational behavior (sequential processing), and parameter semantics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description is vital. It defines the accepted values for flag_status and, most importantly, explains the operational meaning of the mailbox parameter (targets own mailbox if empty).

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 states the purpose concisely using a specific verb ('Set') and resource ('follow-up flag on messages'). This provides immediate clarity on the tool's function and action.

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?

While it doesn't explicitly name alternative tools, it provides important usage constraints, such as the maximum limit of 50 message IDs per call, and defines the default behavior for the mailbox argument.

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