Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

find_similar

Read-onlyIdempotent

Find emails with content similar to a specified email or attachment by providing exactly one email ID or attachment ID, with an optional result limit.

Instructions

Find emails similar in content to an email or to one attachment. Give exactly one of the two ids.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
email_idNoArchive id or Message-ID of an email
attachment_idNoattachment_id from list_attachments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the mutual-exclusivity rule that the schema does not express, but says nothing about how similarity is measured, whether the source email is excluded from results, or how results are ranked - context that would genuinely help an agent interpret output.

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 with no filler: the purpose comes first, the input constraint second. Every clause carries information an agent needs.

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?

For a three-parameter, read-only tool with no output schema this covers the essentials of what it does and how to invoke it. It is thin on what the returned results represent (similarity basis, ordering, whether the seed item appears), which leaves an agent guessing about result interpretation.

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?

With 67% schema coverage, the schema documents email_id and attachment_id but permits both to be null; the description supplies the missing constraint that exactly one must be provided, which is real meaning beyond the schema. The limit parameter and its default/maximum remain undocumented in prose, but the schema covers it adequately.

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 similar in content') and clarifies the input basis (an email or one attachment), which is more specific than a generic search. It does not name or distinguish itself from the plausible siblings semantic_search or search_emails, so an agent must infer the boundary itself.

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?

There is no statement of when to use this tool instead of semantic_search or search_emails, nor any mention of prerequisites or exclusions. The only guidance is the input constraint 'Give exactly one of the two ids,' which governs parameters rather than tool selection.

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