Skip to main content
Glama
Sign In
Email MCP Server

Email MCP Server

by 123jixinyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_watcher_status

Read-only

Monitor IMAP IDLE watcher connections and recent activity. Check if watchers are active and see the latest events.

Instructions

Get the status of IMAP IDLE watcher connections and recent activity.

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": "get_watcher_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which covers safety. The description adds useful context about the tool's focus (IMAP IDLE watcher connections) and that it reports recent activity, going beyond what annotations provide. It does not detail output format, but for a read-only status tool this is acceptable.

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, front-loaded sentence with no redundant words. It conveys the essential purpose and scope efficiently, earning a perfect score for conciseness.

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?

For a zero-parameter, read-only status tool with no output schema, the description is sufficiently complete. It tells the agent what resource is inspected and that recent activity is included. However, it leaves vague what 'status' encompasses (e.g., booleans, counts, timestamps), so it is not perfect.

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?

There are zero parameters, and the schema coverage is 100% (vacuously). Per the guideline, a baseline of 4 applies when there are no parameters to document. The description does not need to explain parameter meanings.

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 specifies the verb 'Get' and the resource 'status of IMAP IDLE watcher connections and recent activity'. It uniquely identifies the tool among siblings, which mostly focus on emails, mailboxes, or calendars, making it distinct as a status/diagnostic tool.

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

Usage Guidelines3/5

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

The usage context is implied: it is a diagnostic tool for inspecting IMAP IDLE watcher connections. However, it does not explicitly state when to use it over related tools like check_health or check_notification_setup, nor does it provide exclusions or alternative recommendations.

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