Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

semantic_search

Read-onlyIdempotent

Find emails and attachments by meaning using natural-language queries, with snippets showing the best-matching passage and whether meaning, keywords, or both matched.

Instructions

Find emails and attachments by meaning. Each result is one email with the best matching passage as its snippet, match says whether that passage is the subject, the body or an attachment, and matched says whether meaning, keywords or both found it.

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": "semantic_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNohybrid: meaning plus keywords, fused (default). semantic: meaning onlyhybrid
limitNo
queryYesWhat you remember, in your own words, in any of about 100 languages. No exact keywords needed
folderNoFolder name contains this text
senderNoFrom: sender name or address contains this text
accountNoAccount name contains this text
date_toNoLatest date, inclusive, YYYY-MM-DD or ISO 8601 (UTC)
date_fromNoEarliest date, YYYY-MM-DD or ISO 8601 (UTC)
recipientNoTo/Cc/Bcc contains this text
has_attachmentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real value by explaining the result envelope (one email per hit, snippet = best passage, match = subject/body/attachment, matched = meaning/keywords/both) and thereby discloses hybrid-mode behavior, but says nothing about ordering, scoring, cost, or result caps.

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?

Three sentences, front-loaded with the action, then the return-shape contract. Every clause carries information, though the second sentence is dense enough that a short bullet or clause break would scan faster.

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 10 parameters, no output schema, and a mutation-free read operation, the description covers the essentials: what it does and what comes back. Missing only result ordering and how `limit`/pagination behaves, which an agent would need to page 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 80%, so nearly every parameter (mode, query, folder, sender, dates, has_attachment) is already documented in the schema with examples and formats. The description adds no parameter-level detail of its own; its `match`/`matched` references describe output fields, not inputs.

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 ('Find emails and attachments') plus the distinguishing mechanism ('by meaning'), which separates it in spirit from keyword search siblings like search_emails. It stops short of naming an alternative tool explicitly, so differentiation is implied rather than stated.

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 phrase 'by meaning' and the schema note 'No exact keywords needed' imply when this tool beats exact-match search, but the description never says when to prefer it over search_emails or find_similar, and gives no exclusions or prerequisites.

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