Skip to main content
Glama
uth-mail-mcp

uth-mail-mcp

by fotispetrou

get_message

Read-only

Retrieve a full email message—headers, plain-text body, and attachments—by UID and folder without marking it as read.

Instructions

A whole message: headers, the text (HTML mail converted to plain text) and its attachments. Reading it does not mark it as read.

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": {
      "uid": "<uid>"
    },
    "name": "get_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidYes
folderNoinbox

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description goes beyond them by disclosing two non-obvious traits: HTML bodies are converted to plain text (so fidelity is lost), and reading does not change the read/unread flag. These are exactly the kind of side-effect facts an agent cannot get from schema or annotations.

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?

Two short sentences, front-loaded with the payload contents and followed by the side-effect caveat. Nothing is redundant, though the opening phrase 'A whole message:' is a label rather than a verb, which blunts first-glance readability.

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?

Because no output schema exists, the description usefully enumerates the return payload (headers, text, attachments), which carries much of the load. However, the parameters remain unexplained and nothing covers missing-uid behavior or how attachments are represented.

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?

Schema description coverage is 0% across two parameters, and the description says nothing about what 'uid' identifies or that 'folder' defaults to 'inbox' and can point elsewhere. The description leaves the caller with bare field names from the schema, so it fails to compensate for the coverage gap.

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?

The description names the resource and enumerates exactly what a 'whole message' contains: headers, plain-text body, and attachments. That is specific enough to separate it from search_messages or download_attachment, though it never explicitly contrasts itself with a sibling.

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 implied (fetching a complete single message) and the note that reading does not mark it as read hints at when an agent can safely peek without side effects. There is no explicit 'use this when... use search_messages instead when...' guidance.

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