Skip to main content
Glama
chandshy

mailpouch

by chandshy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Sync Emails

sync_emails
Idempotent

Fetch recent emails from IMAP into local cache. Refresh the cache after Bridge syncs new messages to make them available for retrieval.

Instructions

Fetch the latest emails from IMAP into the local cache. Use this to refresh the cache after Bridge syncs new messages. Returns emails fetched; use get_emails for paginated access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax emails to fetch (1-500, default 100)
folderNoFolder to sync. Default: INBOX
account_idNoOptional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYes
folderYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.1.0
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Optional account ID to route this call to (multi-account configs). Omit to use the active account. Configured account IDs are listed in the settings UI (Accounts tab).",
+  "type": "string"
+}
  2. First observedv3.0.77

TDQS

A4.5/5.0
Behavior4/5

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

Annotations provide readOnly=false, idempotent=true, destructive=false. Description adds context about cache refresh and return behavior, no contradictions.

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?

Two sentences: one for main action, one for usage guidance and sibling distinction. No fluff.

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?

Has output schema, so return values are covered. Description provides sufficient context for tool usage and parameter behavior.

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 coverage is 100%; description does not add parameter details beyond schema, but baseline for high coverage is 3.

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?

Clearly states verb 'fetch' and resource 'emails from IMAP into local cache'. Distinguishes from sibling 'get_emails' by noting paginated access.

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?

Explicitly says 'Use this to refresh the cache after Bridge syncs new messages' and contrasts with 'get_emails for paginated access'.

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