Skip to main content
Glama
outlook-mcp

outlook-mcp

by Plong-Wasin

get_message

Retrieve a single Outlook message by ID to read its full body as text or HTML, see all recipients, and get attachment metadata such as name, size, and type.

Instructions

Read the full content of a single Message by ID. Returns body (plain text or HTML), all recipients, and attachment metadata (name, size, type — not file content).

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": {
      "messageId": "<messageId>"
    },
    "name": "get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyTypeNoBody format to return: 'text' (default) or 'html'
messageIdYesThe Message ID (from list_messages)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does well: it names the return payload (body as text or HTML, all recipients, attachment metadata) and explicitly bounds it ('not file content'), preventing a wrong assumption about downloading attachments. It stops short of noting behavior on invalid IDs, permission requirements, or message-body truncation.

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 sentences, front-loaded with the action and resource, followed by the return contract. Every clause earns its place, and the 'not file content' caveat is exactly the kind of detail worth the words.

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?

There is no output schema, so the description must describe the response, and it does so adequately (body format, recipients, attachment metadata). For a simple two-parameter read tool this is nearly sufficient; only error/permission behavior is unaddressed.

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 100%, so both parameters are already documented in the schema, including the bodyType enum and where messageId comes from. The description's mention of 'plain text or HTML' merely restates the bodyType option rather than adding new semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read the full content of a single Message by ID') and scopes it to one message, which cleanly separates it from the sibling list_messages. Enumeration of what is returned confirms the intent without ambiguity.

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?

Usage is implied: fetch one message's full content once you have an ID from list_messages (the schema reinforces this). There is no explicit when-to-use vs. when-not guidance and no mention of alternatives such as list_messages for browsing, so the agent must infer routing.

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