Skip to main content
Glama

stop_mail_watch

Disable push notifications for a Gmail mailbox to manage email alerts and reduce interruptions.

Instructions

Stop receiving push notifications for the given user mailbox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:1315-1324 (registration)
    Registration of the 'stop_mail_watch' MCP tool using McpServer.tool(). Includes inline handler function that calls Gmail API's users.stop() via the shared handleTool utility to stop mailbox push notifications.
    server.tool("stop_mail_watch",
      "Stop receiving push notifications for the given user mailbox",
      {},
      async () => {
        return handleTool(config, async (gmail: gmail_v1.Gmail) => {
          const { data } = await gmail.users.stop({ userId: 'me' })
          return formatResponse(data)
        })
      }
    )
  • Inline handler function for 'stop_mail_watch' tool. Uses handleTool to authenticate and execute Gmail API call to stop watching the mailbox for changes.
    async () => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.stop({ userId: 'me' })
        return formatResponse(data)
      })
    }
  • Input schema for 'stop_mail_watch' tool: no parameters required.
    {},
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 mentions the action ('Stop receiving push notifications') which implies a state change operation, but doesn't disclose important behavioral traits like whether this requires specific permissions, whether it's reversible, what happens if no watch exists, or any rate limits. The description is minimal and lacks operational context.

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, clear sentence that efficiently conveys the tool's purpose without any wasted words. It's appropriately sized for a simple tool with no parameters and gets straight to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no parameters, no output schema, and no annotations, the description provides the basic purpose but lacks important context about how the tool behaves operationally. It doesn't explain what 'the given user mailbox' means contextually or what happens after stopping notifications. The description is minimally viable but has clear gaps in operational transparency.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, which is correct for this tool configuration.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Stop receiving push notifications') and the target resource ('for the given user mailbox'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from its sibling 'watch_mailbox' (which presumably starts notifications), though the relationship is implied through naming conventions.

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 description implies usage context (when you want to stop push notifications for a mailbox) but doesn't provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites like needing an active watch to stop. The relationship with 'watch_mailbox' is apparent but not explicitly stated.

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/nk900600/gmail-mcp'

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