Skip to main content
Glama
LeoPhoenixT

readNdraft IMAP MCP

by LeoPhoenixT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_email

Read-onlyIdempotent

Read safe headers and plain text for one email using account, mailbox, UID validity, and UID. Enables read-only message inspection via IMAP.

Instructions

Read safe headers/plain text using one complete returned identity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uidYes
mailboxYes
account_idYes
uid_validityYes
max_text_charsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYes
flagsYes
headersYes
identityYes
attachmentsYes
text_truncatedYes
text_total_charsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.10.0
    • addedOutput schema / $defs / AttachmentMetadataOutput / properties / encoded_size
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Encoded Size"
+}
    • addedOutput schema / $defs / AttachmentMetadataOutput / properties / size / anyOf
      Added value: +[
+  {
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / $defs / AttachmentMetadataOutput / properties / size / type
      Removed value: -"integer"
    • changedOutput schema / $defs / AttachmentMetadataOutput / required
      Previous value: -[
-  "attachment_id",
-  "filename",
-  "content_type",
-  "size"
-]New value: +[
+  "attachment_id",
+  "filename",
+  "content_type",
+  "size",
+  "encoded_size"
+]
  2. Changed4 schema fields changedv0.9.0
    • addedInput schema / properties / max_text_chars
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Max Text Chars"
+}
    • addedOutput schema / properties / text_total_chars
      Added value: +{
+  "title": "Text Total Chars",
+  "type": "integer"
+}
    • addedOutput schema / properties / text_truncated
      Added value: +{
+  "title": "Text Truncated",
+  "type": "boolean"
+}
    • changedOutput schema / required
      Previous value: -[
-  "identity",
-  "headers",
-  "text",
-  "flags",
-  "attachments"
-]New value: +[
+  "identity",
+  "headers",
+  "text",
+  "flags",
+  "attachments",
+  "text_total_chars",
+  "text_truncated"
+]
  3. First observedv0.1.4

TDQS

C2.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that only 'safe headers/plain text' is read, which is useful context, but it does not clarify truncation, what 'safe' means, or any auth/rate-limit behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short for a tool with four required identity parameters and one optional content-limit parameter. It is not bloated, but it is under-specified to the point that brevity is a defect rather than conciseness.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, and annotations cover safety hints. Still, the input identity is completely undocumented in both schema and description, and no usage context is supplied, leaving the definition inadequate for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are five input parameters, four of them required, with 0% schema description coverage. The description does not explain account_id, mailbox, uid_validity, uid, or max_text_chars, and the vague phrase 'one complete returned identity' does not provide usable semantics for the identity tuple.

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

Purpose3/5

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

The description states a verb ('Read') and a narrow content type ('safe headers/plain text'), so it is not a bare tautology. However, it never names the resource as an email and does not distinguish itself from siblings such as get_email_html or get_emails, and the phrase 'using one complete returned identity' is opaque.

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 when-not-to-use guidance, and no named alternative. The phrase 'using one complete returned identity' hints at a prerequisite identity from another call, but it does not identify which call or explain the selection context versus get_email_html, get_emails, or search_emails.

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