Skip to main content
Glama
Sign In
mcp-outlook-lite

mcp-outlook-lite

by w21180239
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

outlook_list_rules

List all inbox message rules in a Microsoft Outlook mailbox so AI agents can review, audit, or manage email filtering and organization.

Instructions

List all inbox message rules

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "outlook_list_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'List', missing details such as permissions required, whether it's read-only (though implied), or what the output contains. For a tool with zero parameters, more context could be provided.

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?

The description is a single short sentence, which is concise and front-loaded. It could be slightly more informative, but it doesn't waste words.

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?

Given the complexity (simple list operation, no parameters, no output schema) and no annotations, the description is adequate but minimal. It doesn't explain what the rules contain or the return format, though an output schema is absent. For a zero-parameter tool, it's borderline complete but lacks helpful context.

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?

There are no parameters (0 count), so the baseline is 4. The description doesn't need to explain parameters, and it doesn't add any misleading information.

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 states a specific verb ('List') and resource ('all inbox message rules'), which is clear. It doesn't explicitly distinguish from siblings like outlook_delete_rule or outlook_create_rule, but the list vs. mutate distinction is obvious.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites or contexts, leaving usage entirely to inference from the name.

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