Skip to main content
Glama
new-outlook-mcp

new-outlook-mcp

by michalhron

get_email

Read-onlyIdempotent

Retrieve a single archived email with its metadata, attachment list, and plain-text body. Page long bodies by offset and limit body size to fit reading needs.

Instructions

Get one email: metadata, attachment list and plain-text body (paged with offset).

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": {
      "email_id": "<email_id>"
    },
    "name": "get_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoBody character offset, for paging long bodies
email_idYesArchive id from search results, or an Internet Message-ID
max_charsNo
include_headersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is in disclosing that the body is plain-text only, that it is paged rather than returned whole, and that only an attachment list - not attachment content - is included. It stops short of describing what happens when offset exceeds the body length or what metadata fields appear.

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?

A single front-loaded sentence that puts the resource first and the returned payload second, with no filler. The parenthetical about paging is slightly compressed but still earns its place.

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?

With no output schema, the description must define the return shape, and it does so at a high level only - the actual metadata fields and attachment-list entry structure are unspecified. For a four-parameter read tool with two undocumented parameters, it is adequate but leaves real gaps.

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 50%: offset and email_id are documented in the schema, while max_chars and include_headers have no descriptions anywhere. The description's 'paged with offset' reinforces the offset parameter but adds nothing about max_chars truncation or what include_headers actually surfaces.

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?

The description names a specific verb and resource ('Get one email') and enumerates exactly what comes back: metadata, attachment list, and plain-text body. It does not distinguish itself from a sibling such as get_thread for whole conversations, so it falls short of a 5.

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 only implied - an agent can infer this is the single-message retrieval path, and the mention of an attachment list hints that attachment content lives elsewhere. There is no explicit when-to-use, no exclusion of thread-level retrieval, and no statement of prerequisites.

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