Skip to main content
Glama
littlebearapps

Outlook Assistant

by littlebearapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Master Categories

manage-category
Destructive

Create, update, list, or delete Outlook categories to organize mail, calendar, and contacts. Deleting a category leaves existing labeled items tagged until cleaned manually.

Instructions

Manage the user's master category list (the colour-coded labels available across mail/calendar/contacts). action=list (default) returns categories with id/displayName/color. action=create adds a new category — displayName required, color optional (preset0-preset24, e.g. preset0=Red, preset7=Blue). action=update (alias set — deprecated) changes name/colour by id. action=delete removes a category — this does NOT untag messages already labelled with it; existing messages retain the orphaned label until manually cleaned. Use apply-category to tag/untag specific messages.

Input Schema

NameRequiredDescriptionDefault
idNoCategory ID (action=update/delete, required)
colorNoColor preset, e.g. preset0=Red, preset7=Blue (action=create/update)
actionNoAction to perform (default: list). 'set' is a deprecated alias for 'update'.
categoryIdNoDEPRECATED: alias for `id`. Will be removed in a future release.
displayNameNoCategory name (action=create required, action=update optional)
outputVerbosityNoOutput detail level (action=list, default: standard)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.9.0
    • changedInput schema / properties / categoryId / description
      Previous value: -"DEPRECATED: alias for `id`. Will be removed in v3.8.0."New value: +"DEPRECATED: alias for `id`. Will be removed in a future release."
  2. Changed4 schema fields changedv3.7.4
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / action / description
      Previous value: -"Action to perform (default: list)"New value: +"Action to perform (default: list). 'set' is a deprecated alias for 'update'."
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "list",
-  "create",
-  "update",
-  "delete"
-]New value: +[
+  "list",
+  "create",
+  "update",
+  "set",
+  "delete"
+]
    • addedInput schema / properties / categoryId
      Added value: +{
+  "description": "DEPRECATED: alias for `id`. Will be removed in v3.8.0.",
+  "type": "string"
+}
  3. First observedv3.4.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, but the description adds genuinely non-obvious behavior: delete does NOT untag messages, leaving orphaned labels until manual cleanup. It also flags the deprecated 'set' alias, which the annotation set cannot convey. It doesn't mention idempotency or permission requirements.

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 dense paragraph that front-loads the resource, then walks actions in a predictable order, closing with the destructive caveat and the sibling redirect. No sentence is redundant.

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?

With no output schema, the description carries the return-shape burden and does so for list (id/displayName/color), but is silent on what create/update/delete return. It compensates well on the destructive-delete semantics, so the gap is minor.

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 coverage is 100% so the baseline is 3, but the description maps parameters to actions ('displayName required' for create, 'color optional', 'id' for update/delete) and repeats the preset0=Red/preset7=Blue decoding, adding conditional-requirement context the flat schema does not surface.

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?

States a specific resource (the user's master category list) and enumerates all four operations with their exact effects. The parenthetical 'the colour-coded labels available across mail/calendar/contacts' disambiguates the resource, and the closing pointer to apply-category separates this tool from the tagging sibling.

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?

Each action is paired with its trigger condition ('action=list (default)', 'action=create adds', 'action=delete removes'), and it explicitly routes tagging/untagging to apply-category. It lacks a stated 'when not to use' or prerequisite/permission guidance, but the action-level routing is clear.

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