Skip to main content
Glama

Categorize messages

categorize_messages

Set, add, or remove categories on Outlook messages by ID to organize and triage mail. Use mailbox category names and choose set, add, or remove mode.

Instructions

Set, add or remove categories on messages. See list_categories for the mailbox's category names.

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>",
      "categories": "<categories>"
    },
    "name": "categorize_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesMessage IDs (from list_messages, search_messages or get_message)
modeNo"add" (default) keeps existing categories, "set" replaces them, "remove" removes the given ones
categoriesYesCategory names

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is supplied structurally. The description adds the meaningful behavioral note that 'set' replaces while 'add'/'remove' modify incrementally, plus the prerequisite of looking up names via list_categories, but it stays silent on what happens with unknown categories or what the call returns.

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?

Two short sentences with no filler. The primary capability is front-loaded and the pointer to list_categories follows immediately.

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 three-parameter tool with full schema coverage and annotations covering safety, the description supplies the essentials plus the dependency on list_categories. It is only slightly short of complete because it never says how unknown or absent category names are handled.

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 schema already documents ids, categories, and the mode enum including its default of 'add' and the semantics of each value. The description only restates the three mode verbs, adding no syntax, limits, or format detail beyond the schema.

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 gives a concrete verb set (set/add/remove) applied to a concrete resource (categories on messages), which is exactly what the tool does. It also distinguishes itself from the related listing tool by pointing at list_categories for names, so an agent can separate the mutating tool from the enumeration tool.

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?

Usage context is clear: use this to change categories on messages, and consult list_categories first to discover valid category names. There are no explicit exclusions or stated when-not-to-use conditions, and the choice among set/add/remove is left to the schema rather than the description.

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