Skip to main content
Glama

Outlook Search Mail

outlook_search_mail
Read-only

Search recent Outlook mail by subject, sender, or body; an empty query returns the newest messages.

Instructions

Search recent mail by subject, sender, or body. An empty query returns the newest messages.

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_search_mail"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
folderNoInbox

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds two real behavioral facts: results are limited to recent mail, and an empty query falls back to newest messages. It omits ordering, result cap behavior, and any hint about pagination, so it adds value without being rich.

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, no filler, with the core capability front-loaded and the empty-query fallback immediately after. Every sentence earns its place.

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?

An output schema exists, so return values need not be described. Still, for a three-parameter search tool with zero schema documentation, the description should clarify what 'recent' means, what folder scoping does, and what limit caps — none of which appear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for three parameters, so the description must carry the burden. It partially explains 'query' (subject, sender, or body matching) and the empty-string default, but says nothing about 'folder' (which defaults to Inbox) or 'limit' (default 20), leaving two of three parameters semantically opaque.

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 gives a specific verb and resource ("Search recent mail") plus the searchable fields (subject, sender, body), which clearly separates it from outlook_read_mail or outlook_send_mail. It stops short of naming a sibling alternative, so it is clear but not maximally differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Search recent mail" plus "An empty query returns the newest messages" implies when the tool is useful (browse-by-default, query to narrow). However, there is no explicit guidance on when to prefer outlook_read_mail or outlook_list_folders, and no mention of the 'recent' window that bounds results.

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