Skip to main content
Glama

Read message

get_message
Read-only

Retrieve a Microsoft 365 email with full body, recipients, and attachment details; optionally mark it as read or choose text/HTML body format.

Instructions

Get a message with full body (a string; see bodyFormat), recipients and file attachments (inline images are only counted; list_attachments shows them). Does not mark it read unless markAsRead is true.

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

Input Schema

NameRequiredDescriptionDefault
idYesMessage ID
formatNoBody format: "text" (default) or "html"
markAsReadNoAlso mark the message as read (default false)
maxBodyCharsNoTruncate the body after this many characters (default 20000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description still adds real behavior: it does not mark the message read unless markAsRead is true, and inline images are only counted rather than returned. That is exactly the kind of side-effect disclosure an agent needs before invoking a nominally read-only tool.

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 dense sentence that front-loads the return payload and tucks secondary caveats into parentheticals. Every clause carries information (body type, recipients, attachments, inline-image caveat, read-state condition); nothing is padding.

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 no output schema, the description carries the burden of describing return contents and does so (body string, recipients, attachment list, inline images counted). Combined with annotation coverage of safety and full schema coverage of parameters, an agent has enough to call it correctly; only pagination/size behavior of the returned body is lightly handled via maxBodyChars in the schema.

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 coverage is 100%, so formats, defaults, and the 200-char minimum through 500,000-char maximum truncation bounds are already documented in structured fields. The description adds only the pointer to format selection and the markAsRead default, both of which the schema already states, so baseline 3 applies.

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?

Specific verb+resource: gets a message and enumerates what comes back (full body, recipients, file attachments), and distinguishes itself from list_attachments for inline images. Small blemish: it points to a 'bodyFormat' parameter that does not exist in the schema (the parameter is 'format'), which could momentarily confuse an agent.

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 by the content: use it to read a single message's body and attachments, and use list_attachments when inline images matter. There is no explicit when-not guidance or named alternative for the common read-vs-list choice (e.g., list_messages, get_thread), so an 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.