Skip to main content
Glama
uth-mail-mcp

uth-mail-mcp

by fotispetrou

mark_messages

Idempotent

Mark emails as read or unread and flagged or unflagged in a specified folder, enabling mailbox status updates through IMAP.

Instructions

Mark messages as read or unread (read) and/or flagged or not (flagged).

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": {
      "uids": "<uids>"
    },
    "name": "mark_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
readNo
uidsYes
folderNoinbox
flaggedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare this is a non-readonly but idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description usefully clarifies that both attributes can be set in one call ('and/or'), but says nothing about what happens when both flags are null, whether folder is auto-created, or what the call returns on partial failure.

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?

A single tight sentence with no filler, and the actionable content is front-loaded. It is efficient, though the brevity comes at the cost of the usage and parameter detail noted elsewhere.

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?

There is no output schema to explain and annotations cover the mutation semantics, which limits what is strictly required. Still, for a 4-parameter mutation with 0% schema coverage, the definition omits the meaning of the required `uids` and the `folder` scoping parameter, which an agent needs before calling it.

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 coverage is 0%, so the description carries the burden. It does add real meaning for `read` and `flagged` by spelling out that true/false map to read/unread and flagged/not, which the raw booleans do not convey. However, the required `uids` array and the `folder` parameter (default 'inbox') get no explanation at all, leaving half the parameters — including the only required one — undocumented.

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 ('Mark') and resource ('messages'), and enumerates the two state axes it controls (read/unread, flagged/not). It is distinguishable from siblings like move_messages or search_messages, but it does not explicitly name an alternative or scope (folder) to sharpen the contrast.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention that at least one of `read`/`flagged` must be supplied to do anything, and no statement of prerequisites such as the target folder existing or the uids needing to be valid. The agent is left to infer invocation conditions entirely from the schema defaults.

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