Skip to main content
Glama

get_email

Retrieve detailed information about a specific Outlook email by message ID to view its content, metadata, and status. Use the message ID to target the exact message.

Instructions

Get detailed information about a specific email

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

Input Schema

NameRequiredDescriptionDefault
message_idYesThe ID of the email message

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about side effects (e.g., whether fetching marks the message as read), required permissions or auth/scope, or what happens for an invalid or inaccessible ID. "Get" weakly implies a read, but that is inference rather than disclosure.

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 filler, though it is on the sparse side for a tool with zero annotation support.

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?

For a simple one-required-parameter tool with a fully documented schema and no output schema, the description is minimally sufficient. It still leaves open what "detailed information" includes and whether reading triggers state changes, which matters for an unannotated 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 description coverage is 100%, with message_id fully documented as "The ID of the email message," so the baseline is 3. The description adds no format, source, or sourcing guidance beyond what the schema already states.

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?

"Get detailed information about a specific email" names a concrete verb (get) and resource (email) and scopes it to a single message via message_id. This implicitly separates it from list_emails and search_emails, though it never names those siblings explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit when-to-use, when-not-to-use, or alternative routing. An agent must infer from the word "specific" that it needs a known message_id and that discovery should go through search_emails or list_emails first.

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