Skip to main content
Glama

Flag messages

flag_messages

Set or clear follow-up flags on specified Outlook messages by ID, marking them flagged, complete, or none for triage tracking.

Instructions

Set the follow-up flag on messages.

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>",
      "status": "<status>"
    },
    "name": "flag_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage IDs (from list_messages, search_messages or get_message)
statusYes"flagged", "complete" or "none" (clear)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds nothing beyond that: it does not say the change is reversible, that it applies in bulk (the schema allows up to 500 IDs), or that it overwrites prior flag state rather than appending. For a mutation tool this is a thin addition.

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 front-loaded sentence with zero padding or redundancy. Its brevity is efficient rather than wasteful, though it borders on under-specification for a state-mutating batch tool.

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?

With only two fully documented parameters, rich annotations, and no output schema, the definition is minimally adequate — the agent can call it correctly from the schema. What is missing is the semantics of the tri-state status and the bulk-apply behavior, which the description could have supplied cheaply.

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%, and the status parameter already documents the three enum values, so the schema carries the parameter semantics. The description's phrase "follow-up flag" loosely gestures at status but does not clarify that "complete" and "none" (clear) are equally valid operations, so it adds no meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a verb ("Set") and a resource ("the follow-up flag on messages"), so the general purpose is graspable. However, the tool is really a tri-state follow-up status setter (flagged / complete / none per the status enum), and the description's framing of "flag" makes the clearing and completion behaviors invisible. It also gives no cue distinguishing it from nearby tools like mark_messages_read or categorize_messages.

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 guidance, no prerequisites, and no mention of alternatives. The agent must infer from the name alone that this is the tool for follow-up tracking rather than read/unread or category state.

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