Skip to main content
Glama
Sign In
your-mail-mcp

your-mail-mcp

by wildsurfer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

show

Read-only

Retrieve a single email by Message-ID as JSON with headers and decoded body, plus byte offsets to read long messages in chunks and optional access to junk or trash.

Instructions

Show one message: headers and decoded body, as JSON.

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

Input Schema

NameRequiredDescriptionDefault
idYesMessage-ID of the message, as search, ids and show report it, with or without the surrounding angle brackets.
limitNoHow many bytes of text to return at most. Defaults to 65536, which is also the ceiling.
offsetNoByte offset to resume the text from. Use the offset named in a [truncated] marker to read the next chunk of a long message. Defaults to 0, the start.
include_excludedNoSet true to read a message that lives in junk or trash, which are left out by default. Use it only when the message is expected to be there, since mail in those folders is more likely to be hostile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • addedInput schema / properties / id / description
      Added value: +"Message-ID of the message, as search, ids and show report it, with or without the surrounding angle brackets."
    • addedInput schema / properties / include_excluded / description
      Added value: +"Set true to read a message that lives in junk or trash, which are left out by default. Use it only when the message is expected to be there, since mail in those folders is more likely to be hostile."
    • addedInput schema / properties / limit / description
      Added value: +"How many bytes of text to return at most. Defaults to 65536, which is also the ceiling."
    • addedInput schema / properties / offset / description
      Added value: +"Byte offset to resume the text from. Use the offset named in a [truncated] marker to read the next chunk of a long message. Defaults to 0, the start."
  2. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that the body is decoded and output is JSON, which is useful beyond the structured fields. However, it never mentions the truncation/pagination behavior or the default exclusion of junk/trash mail, both of which shape results.

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 sentence with zero waste; the resource (one message) and the return shape (headers plus decoded body as JSON) are front-loaded.

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?

With no output schema, the description does the right minimum by saying what comes back (headers and decoded body, JSON). Since annotations and a fully documented schema cover safety, pagination and folder defaults, only the missing mention of chunked reading keeps this below 5.

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% — the id, limit, offset and include_excluded parameters are each fully documented in the schema, including the [truncated] marker convention. The description adds nothing about parameter formats or constraints, so the baseline 3 applies.

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 — 'Show one message' — and specifies the payload ('headers and decoded body, as JSON'), which separates it from a plain body-reader. It does not name the sibling tools (text, thread, attachment) it must be distinguished from, so an agent still has to infer the boundary.

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 by the required 'id' parameter: fetch a single known message by Message-ID. There is no explicit when-to-use versus text/thread/attachment, and no statement of prerequisites. Some operational guidance (truncation resumption, junk/trash opt-in) exists, but it lives in the schema rather than the description.

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

Deploy Server

Other Tools