Skip to main content
Glama

ews_get_message

Read-onlyIdempotent

Fetch full email content via Exchange Web Services using an EWS item ID to read complete message details.

Instructions

Get full email content via Exchange Web Services using an EWS item ID.

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": {
      "item_id": "<item_id>"
    },
    "name": "ews_get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesEWS Item ID
account_idNoAccount identifier (defaults to `"default"`)default

Output Schema

NameRequiredDescriptionDefault
dataYesTool-specific data payload
metaYesExecution metadata (timestamp, duration)
summaryYesHuman-readable summary of the operation outcome

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.12

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description's one addition is that it returns 'full' content rather than a summary, but it says nothing about behavior on an invalid/expired item ID or about account scoping beyond the schema default.

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 with no redundant phrasing. It is efficient, though the terseness comes at the cost of the guidance noted in other dimensions.

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?

The tool is simple (2 params, full schema coverage, output schema present, annotations present), so little prose is required. The main missing piece is telling the agent where a valid EWS item ID comes from, which matters for a lookup-by-ID tool.

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 both parameters are already documented in the schema. The description only restates that an EWS item ID is required and adds no format, sourcing, or ID-type detail; account_id goes entirely unmentioned.

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 ('Get full email content') plus the transport ('via Exchange Web Services') and the key input ('EWS item ID'). The EWS framing implicitly separates it from the sibling imap_get_message, but the description never says so explicitly.

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 it should be called when it already holds an EWS item ID and wants the complete message. There is no statement of when to prefer this over imap_get_message or imap_get_message_raw, and no note on where an item ID should come from.

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