Skip to main content
Glama
csitte

mailwarden

by csitte
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

triage_digest

Read-only

Get a structured inbox summary grouped by sender, label, age, and automated-signal flags, with unread and attachment counts, so you can quickly decide what to archive, snooze, or label.

Instructions

Structured overview of a mailbox slice for triage DECISIONS — sender / label / age buckets, unread and attachment counts, and header-derived signals (newsletter / automated / calendar / replyToMismatch — thread counts overall, and per sender the set of signals its threads carry), instead of a raw thread list. USE WHEN: deciding what to bulk-archive/snooze/label, or summarizing inbox state ('what's in my inbox?'). DO NOT USE: to read a specific thread (use search/get_thread). Samples up to max most-recent matches; hasMore flags that more matched than were sampled. byAge buckets by each thread's FIRST message date (thread age, not last activity). SIDE EFFECTS: none.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNo
topNNo
queryNoin:inbox

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
byAgeYes
queryYes
unreadYes
hasMoreYes
sampledYes
signalsYes
topLabelsYes
topSendersYes
withAttachmentsYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv0.11.0
    • addedOutput schema / properties / signals
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "automated": {
+      "type": "number"
+    },
+    "calendar": {
+      "type": "number"
+    },
+    "newsletter": {
+      "type": "number"
+    },
+    "replyToMismatch": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "newsletter",
+    "automated",
+    "calendar",
+    "replyToMismatch"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / topSenders / items / properties / signals
      Added value: +{
+  "items": {
+    "enum": [
+      "newsletter",
+      "automated",
+      "calendar",
+      "replyToMismatch"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / topSenders / items / required
      Previous value: -[
-  "sender",
-  "name",
-  "count",
-  "unread"
-]New value: +[
+  "sender",
+  "name",
+  "count",
+  "unread",
+  "signals"
+]
    • changedOutput schema / required
      Previous value: -[
-  "query",
-  "sampled",
-  "hasMore",
-  "unread",
-  "withAttachments",
-  "byAge",
-  "topSenders",
-  "topLabels"
-]New value: +[
+  "query",
+  "sampled",
+  "hasMore",
+  "unread",
+  "withAttachments",
+  "byAge",
+  "signals",
+  "topSenders",
+  "topLabels"
+]
  2. Addedv0.6.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, but the description adds valuable behavioral details: sampling up to 'max' with hasMore, age bucketing by first message date, and explicit 'SIDE EFFECTS: none'. This goes beyond annotations and answers likely agent questions.

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?

The description is dense yet well-organized into clear sections: overview, use cases, behavior, and side effects. Every sentence contributes new information, with no redundancy or filler.

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?

The description covers the tool's purpose, usage, sampling, age bucketing, and side effects, while an output schema likely handles return-value documentation. However, it leaves parameter semantics incomplete (especially topN/query), a notable gap given the low schema coverage.

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%, so the description must explain parameters. It only mentions 'max' (sampling limit) but leaves 'topN' and 'query' undefined. This forces the agent to infer their meaning, which is insufficient for correct invocation.

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 clearly states it provides a structured overview of a mailbox slice for triage decisions, listing specific aggregated fields (sender/label/age buckets, counts, signals) and explicitly contrasts with a raw thread list. It also distinguishes from reading a specific thread by referencing search/get_thread.

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

Usage Guidelines5/5

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

Includes explicit 'USE WHEN' and 'DO NOT USE' sections, naming alternatives (search/get_thread) and giving concrete examples like bulk-archiving/snoozing/labeling. This provides clear guidance on when to choose this tool over siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/csitte/mailwarden'

If you have feedback or need assistance with the MCP directory API, please join our Discord server