Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes

start_watch

Start real-time monitoring of your IMAP email inbox using IDLE watch to receive immediate notifications for new messages.

Instructions

Start permanent IDLE watch on INBOX, next, waiting, someday

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual implementation of the start_watch method which initiates the watcher.
    def start_watch(self) -> bool:
        """Start permanent IDLE watch on INBOX, next, waiting, someday."""
        if not self.watcher:
            config_path = Path(self.config.get("_config_path", "config.json"))
            self.watcher = get_watcher(str(config_path))
    
        self.watcher.start()
        self.watching = True
        return True
  • Registration of the start_watch tool definition.
    make_tool(
        "start_watch",
        "Start permanent IDLE watch on INBOX, next, waiting, someday",
        {},
    ),
  • The handler logic in the server to invoke the start_watch method on the imap_client.
    elif name == "start_watch":
        return imap_client.start_watch()
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'permanent' and 'IDLE watch', hinting at a long-running or continuous operation, but fails to detail critical aspects such as what 'IDLE' entails, how the watch interacts with the system, potential side effects, or any performance implications like resource usage or rate limits.

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 a single, compact sentence that directly states the tool's action and target without fluff. It's front-loaded with the key verb 'Start', making it easy to parse, though it could be slightly clearer by elaborating on 'IDLE watch' to improve understanding.

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?

Given the complexity implied by terms like 'permanent IDLE watch' and the lack of annotations and output schema, the description is insufficient. It doesn't explain what the watch does, how it behaves, what it monitors, or what outputs or states result from its use, leaving significant gaps in understanding for effective tool invocation.

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

Parameters4/5

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

The tool has 0 parameters, and the schema description coverage is 100%, so no parameter information is needed. The description appropriately avoids discussing parameters, making it efficient and focused on the tool's purpose without unnecessary details.

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 action ('Start permanent IDLE watch') and target ('on INBOX, next, waiting, someday'), which clarifies what the tool does. However, it's somewhat vague about the exact nature of an 'IDLE watch' and doesn't explicitly distinguish this tool from its sibling 'idle_watch' or 'stop_watch', leaving room for confusion about their differences.

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 explicit guidance is provided on when to use this tool versus alternatives like 'idle_watch' or 'stop_watch'. The description implies it's for initiating a watch, but it doesn't specify prerequisites (e.g., whether authentication or connection is needed first) or contextual constraints, offering minimal usage direction.

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/Soundhannes/IMAP-MCP'

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