Skip to main content
Glama

Outlook Read Mail

outlook_read_mail
Read-only

Retrieves the full content of a single Outlook email using the entry_id returned by mail search, so you can read a specific message from the local Outlook profile.

Instructions

Read one message by the entry_id returned from search_mail.

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": {
      "entry_id": "<entry_id>"
    },
    "name": "outlook_read_mail"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 the safety profile is covered elsewhere. The description adds only the narrow constraint that lookup is keyed on an entry_id from search_mail; it says nothing about folder scope, permissions, or what happens when the id is stale or missing, though the output schema relieves it of return-value detail.

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?

A single sentence that front-loads the verb and resource and attaches the one qualifying constraint. Nothing is redundant or padded.

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?

For a simple single-parameter read tool with annotations covering safety and an output schema covering return values, this is nearly sufficient. The remaining gap is minor: nothing on error or empty-result behavior when the entry_id no longer resolves.

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 schema contributes only a bare string type for entry_id. The description compensates partially by tying the value's provenance to search_mail, which is genuinely useful for constructing the argument, but it does not describe the id's format or behavior when invalid.

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 ('Read one message') and scopes it to a single item retrieved by entry_id, which cleanly separates it from the bulk-oriented outlook_search_mail sibling. It stops short of naming the sibling as an explicit alternative, but the read-one-vs-search distinction is clear.

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 the entry_id returned from search_mail' implies the intended workflow (search first, then read), which is genuine usage context. However, it does not explicitly say when not to use it, nor name outlook_search_mail as a formal alternative, leaving the guidance implied rather than stated.

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