Skip to main content
Glama

get_message

Read-only

Retrieves a mail message's headers, truncated plain-text body, and numbered attachment names and sizes. Attachment content is excluded; use get_mail_attachment for that.

Instructions

Get one message: headers, plain text body (cut at 100000 characters) and the numbered names and sizes of attachments. Attachment content is not returned here. Use get_mail_attachment for that.

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 from search_mail.
in_accountNoAccount id of the message (the 'account_id' field of search_mail). Only needed with 'in_mailbox'.
in_mailboxNoMailbox path of the message (the 'mailbox' field of search_mail). Only needed when Full Disk Access is missing. Give 'in_account' too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/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, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the body is truncated at 100000 characters and attachment content is deliberately omitted, only names and sizes being returned. It stops short of describing what happens for messages with no plain text part.

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?

Three short sentences, front-loaded with the return content and then the exclusion, with zero filler. Every sentence carries information an agent would otherwise have to discover by calling the tool.

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?

For a read tool with no output schema, the description does well by naming the returned parts and the truncation limit. Minor gap: it does not say whether an HTML body exists or is discarded, which matters for an agent deciding if this is sufficient for a given message.

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 each of id, in_account, and in_mailbox documented in place, including the conditional relationship between in_account/in_mailbox. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource ('Get one message') followed by an enumeration of exactly what is returned: headers, plain text body, and numbered attachment names and sizes. This distinguishes it clearly from siblings such as get_mail_attachment and search_mail.

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

Usage Guidelines4/5

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

Explicitly routes attachment content retrieval to get_mail_attachment, which is the one obvious alternative an agent might confuse it with. It does not state a when-not condition relative to search_mail or how the 'id' should be obtained in prose, though the schema covers the latter; guidance is clear but not exhaustive.

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