Skip to main content
Glama
Soundhannes

IMAP MCP Server

by Soundhannes

stop_watch

Terminates the real-time IDLE watch that monitors an IMAP mailbox for new email notifications, ending continuous connection monitoring.

Instructions

Stop the permanent IDLE watch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The actual handler implementation for the stop_watch tool in the IMAP client.
    def stop_watch(self) -> bool:
        """Stop the permanent IDLE watch."""
        if self.watcher:
            self.watcher.stop()
        self.watching = False
        return True
  • Registration of the stop_watch tool in the MCP server.
    make_tool(
        "stop_watch",
        "Stop the permanent IDLE watch",
        {},
  • Tool handler dispatch logic in the MCP server.
    elif name == "stop_watch":
        return imap_client.stop_watch()
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool stops a watch, implying a mutation/control action, but doesn't disclose behavioral traits like whether this requires specific permissions, if it's reversible, what side effects occur (e.g., does it terminate background processes?), or error conditions. The term 'permanent' hints at irreversibility but isn't elaborated.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action ('Stop'), making it immediately clear. Every part of the sentence contributes to understanding the tool's function.

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 tool has no parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'IDLE watch' is, what system it operates on, what happens after stopping (e.g., does it return status?), or error handling. For a control tool with zero structured context, more detail is needed to be fully helpful.

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 schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter semantics, but that's acceptable here. Baseline is 4 for zero parameters, as there's nothing to compensate for.

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 'Stop the permanent IDLE watch' states a clear action (stop) but is vague about what 'permanent IDLE watch' refers to. It distinguishes from sibling 'start_watch' and 'idle_watch' by indicating a stopping action, but doesn't specify what resource or system this watch belongs to, leaving the purpose somewhat ambiguous.

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 on when to use this tool versus alternatives is provided. The description implies it should be used to stop a watch, but doesn't specify prerequisites (e.g., must have an active watch), when not to use it, or what happens if invoked without a running watch. It mentions 'permanent' but doesn't clarify if this is a one-time stop or if it affects future sessions.

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