Skip to main content
Glama

mail_get

Read-only

Retrieve a full Outlook message by ID, including its plain-text body and attachment list.

Instructions

Read one message in full (plain-text body), with its attachment list.

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": "mail_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
message_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine context by stating the body is plain-text and that an attachment list is included, which clarifies output shape. It does not say whether attachments are downloaded, what happens on a missing/inaccessible message, or whether anything is truncated.

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 front-loaded sentence with the key qualifiers (full body, plain-text, attachment list) and zero filler. Nothing extraneous and nothing buried.

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?

An output schema exists, so return values need no explanation here. However, for a read tool whose only input is an opaque ID, the description leaves the ID's origin and message-not-found behavior unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

One parameter with 0% schema description coverage and only a 'Message Id' title. The description never explains the expected ID format or where to obtain it, leaving the sole required input under-specified.

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: 'Read one message in full' clearly scopes to a single message, distinguishing it implicitly from list/search siblings by the word 'one'. It does not explicitly name mail_list or mail_search as the source of message IDs, so no sibling differentiation by name.

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: the phrase 'one message in full' suggests fetching a single item after a listing/search step, but no when-to-use, when-not-to-use, or named alternative is given. The agent must infer that message_id comes from mail_list or mail_search.

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