Skip to main content
Glama
malamutemayhem

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailroom_read

Read-onlyIdempotent

Read one message by ID to retrieve headers, plain-text body, and attachment list; optionally include the HTML body and target a folder or connected account.

Instructions

Read one message: headers, plain-text body and the list of attachments.

Input Schema

NameRequiredDescriptionDefault
idYesMessage id from mailroom_search (a numeric uid for Gmail/IMAP, a Graph id for Microsoft 365).
folderNoFolder: inbox (default), sent, drafts, trash, junk, archive, all, or a folder name.
accountNoWhich connected mailbox to use (its label from mailroom_accounts). Optional when only one is connected or a default is saved in memory.
include_htmlNoAlso return the HTML body when the message has one (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive behavior. The description adds useful return-shape context, notably that it returns headers, plain-text body and an attachment list rather than attachment contents or HTML.

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?

It is a single front-loaded sentence with no wasted words. The key action and returned data are stated immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-by-id tool, the definition is complete when combined with the annotations and fully described schema. The description covers the essential behavioral context: what is returned.

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%, so all four parameters are already well documented in the schema. The description adds no parameter-specific meaning beyond the schema.

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?

The description names a specific verb and resource: reading one message. It also states the returned content (headers, plain-text body, attachment list), which distinguishes it from message-search and attachment-specific siblings.

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 by 'Read one message', and the id parameter in the schema points to mailroom_search as the source. However, the description itself does not explicitly say when to use this versus mailroom_search or mailroom_attachment.

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