Skip to main content
Glama
littlebearapps

Outlook Assistant

by littlebearapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Focused Inbox

manage-focused-inbox
Destructive

List, create, or delete Focused Inbox sender overrides to route emails from specific senders to Focused or Other.

Instructions

Manage Focused Inbox sender overrides — explicit rules that force messages from a given sender into Focused or Other regardless of the ML classifier. action=list (default) returns existing overrides with id/sender/classifyAs. action=set creates or updates an override for emailAddress (optional name), routing future mail to focused (default) or other. action=delete removes the override for emailAddress. Note: this only works on accounts that have Focused Inbox enabled — personal Outlook.com accounts without it return an empty list.

Input Schema

NameRequiredDescriptionDefault
nameNoSender display name (action=set)
actionNoAction to perform (default: list)
classifyAsNoWhere to put emails from this sender (action=set, default: focused)
emailAddressNoSender email address (action=set/delete, required)
outputVerbosityNoOutput detail level (action=list, default: standard)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.9.1
  2. Removedv3.9.0
  3. Changed1 schema field changedv3.7.4
    • addedInput schema / additionalProperties
      Added value: +false
  4. First observedv3.4.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and idempotentHint=false, and the description adds substance on top: delete removes the override, set creates or updates, and accounts lacking Focused Inbox silently return an empty list rather than erroring. That last caveat is genuine context an annotation cannot convey.

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?

Front-loaded with the resource definition, then three tight action clauses, then the account caveat. No sentence is redundant and the ordering matches how an agent would reason about the call.

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?

With no output schema, the description usefully names the returned fields for list (id/sender/classifyAs), covers defaults for every optional parameter, and discloses the empty-list edge case. An agent has everything needed to pick an action and call it correctly.

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 defaults, enums and which action each parameter belongs to, so the baseline is 3. The description restates those mappings and clarifies that emailAddress is the keying field, but adds no syntax 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?

States a specific verb+resource ('Manage Focused Inbox sender overrides') and immediately defines the resource as explicit per-sender rules that override the ML classifier, which cleanly separates it from generic siblings like manage-rules. The three action values are enumerated with their effects.

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?

Gives clear per-action conditions (list=default, set=create/update for emailAddress, delete=remove) plus a real prerequisite: the account must have Focused Inbox enabled. It stops short of explicitly routing the agent away from manage-rules or mailbox-settings when a user actually wants general rule configuration.

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