Skip to main content
Glama

mail_search

Read-only

Search Outlook mail using Outlook search syntax to locate messages by sender, subject, attachment status, or date; results are ranked by relevance.

Instructions

Search all mail with Outlook search syntax, e.g. invoice, from:amazon, subject:"tax return", hasattachments:true dentist, received>=2026-10-01. Results are ranked by relevance.

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": {
      "query": "<query>"
    },
    "name": "mail_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description still adds real behavior beyond the annotations: the scope is all mail (not a single folder) and results are relevance-ranked rather than chronological, which affects how an agent interprets output.

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?

Purpose is front-loaded in the first clause, and the example set is dense but each example demonstrates a distinct operator. The sentence does not sprawl, though the sample-query list is doing most of the work and could be tightened slightly.

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 an output schema present, return values need no explanation, and annotations cover the read-only profile. The only material gap is the unexplained `top` parameter and the absence of any guidance about result volume or pagination on a tool that searches all mail.

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 0%, so the description must carry parameter meaning; it does this well for `query` by giving five concrete syntax forms. However, `top` (default 15) is never mentioned, so result-count control is undocumented in both the schema and the description.

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?

States a specific verb and resource ("Search all mail") and pins the query dialect to Outlook search syntax with concrete examples. That is enough to distinguish it from mail_get or mail_list, though the description never explicitly says how it differs from browsing via mail_list.

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?

The syntax examples imply how to build queries, but there is no explicit when-to-use guidance (e.g., use this for ad-hoc queries vs. mail_list for enumerating a folder) and no stated limits or fallback behavior. Usage is inferable rather than directed.

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