Skip to main content
Glama
Sign In
MailOKF MCP

MailOKF MCP

by pat229988
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mail_sync_all

Synchronize every enabled email account across Gmail, Outlook, iCloud, and IMAP mailboxes in one action to keep your OKF knowledge layer up to date with the latest provider-side changes.

Instructions

Synchronize every enabled account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "mail_sync_all"
  }
}

Input Schema

NameRequiredDescriptionDefault
fullNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Synchronize every enabled account' gives no indication of duration expectations, rate limits, whether it can be run concurrently with other sync operations, what happens to in-progress syncs, or error behavior. For a potentially long-running batch operation touching all accounts, this is a significant gap.

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?

The description is appropriately short at seven words with no wasted content. However, this brevity borders on under-specification rather than effective conciseness, since it omits the parameter semantics and usage context that other dimensions need.

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?

Despite having an output schema, this tool performs an operation across all accounts and has one boolean parameter that is entirely undocumented. The description fails to explain the behavioral implications of a batch sync (time cost, system load), what 'full' controls, or how to interpret the result. For a batch operation with a subtletly-named parameter, the description is insufficiently complete.

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 the 'full' boolean parameter. It doesn't. The description says 'every enabled account' and 'full' defaults to false, but there's zero explanation of what full vs non-full synchronization means or what toggling it does. The description adds virtually no semantic value for the single parameter.

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 the verb 'Synchronize' and resource 'every enabled account', which conveys the core purpose. However, it doesn't clearly distinguish from sibling tools mail_sync_initial and mail_sync_now, which likely perform different synchronization modes. The word 'every' adds some scope specificity but leaves ambiguity about what full versus incremental sync means.

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?

No guidance on when to use this tool versus mail_sync_now or mail_sync_initial. The siblings suggest different sync granularities (initial, now, all), but the description provides no comparison or exclusion guidance. An agent has no way to determine which sync tool fits a given scenario.

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