Skip to main content
Glama

flag_message

Idempotent

Flag or unflag up to 100 messages by ID, optionally setting a color; if Mail is closed, it opens hidden in the background to apply the change.

Instructions

Flag or unflag messages (at most 100). Give 'color' to flag with a color. Without 'color', Mail uses its default flag. If Mail is not running, applesauce opens it hidden in the background and leaves it open.

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": {
      "ids": "<ids>",
      "flagged": "<flagged>"
    },
    "name": "flag_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage ids from search_mail. At most 100.
colorNoFlag color. Needs 'flagged' true.
flaggedYestrue to flag, false to remove the flag.
in_accountNoAccount id of the message (the 'account_id' field of search_mail). Only needed with 'in_mailbox'.
in_mailboxNoMailbox path of the message (the 'mailbox' field of search_mail). Only needed when Full Disk Access is missing. Give 'in_account' too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the tool non-read-only, idempotent and non-destructive, so the safety profile is covered. The description still adds genuinely useful behavior beyond that: it discloses the hidden background launch of Mail and the fact that Mail is left open, and it explains that omitting 'color' still produces a default flag rather than no flag.

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?

Three short, front-loaded sentences with no filler. The batch-limit clause is attached parenthetically and the side-effect note is last, which is a sensible ordering, though the side-effect sentence is slightly tangential to the primary operation.

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 five-parameter mutation tool with no output schema, the definition covers the essentials an agent needs: what it does, the batch limit, the meaning of the optional color, and a notable environment side effect. The only real gap is the Full Disk Access / mailbox fallback path, which is left entirely to the schema.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema doesn't: the interaction between 'color' and default flagging, and the batch ceiling. It doesn't restate the enum or explain the in_account/in_mailbox fallback, which are only in the schema.

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 opens with a specific verb pair and resource ('Flag or unflag messages'), immediately tells the agent that flagging and unflagging are the same operation, and caps the batch at 100. It doesn't explicitly contrast itself with any sibling, but no sibling in the list performs flagging, so ambiguity is low.

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?

The description explains the conditional behavior of the 'color' parameter, which is useful usage guidance, but it doesn't say when to prefer this tool over alternatives or what prerequisites (account, mailbox) the agent must satisfy. The mailbox/account fallback scenario is covered only in the schema, not the description.

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