Skip to main content
Glama

stop_mail_watch

Disable push notifications for a Gmail mailbox to stop receiving real-time email alerts.

Instructions

Stop receiving push notifications for the given user mailbox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for the 'stop_mail_watch' tool. Authenticates via handleTool and calls Gmail API's users.stop to cease push notifications on the user's mailbox.
    async () => {
      return handleTool(config, async (gmail: gmail_v1.Gmail) => {
        const { data } = await gmail.users.stop({ userId: 'me' })
        return formatResponse(data)
      })
    }
  • src/index.ts:1296-1305 (registration)
    Registration of the 'stop_mail_watch' MCP tool with empty input schema and inline handler implementation.
    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)
        })
      }
    )
  • Empty input schema for the 'stop_mail_watch' tool (no parameters required).
    {},
  • Shared helper function 'handleTool' used by stop_mail_watch (and other tools) for OAuth2 authentication, credential validation, Gmail client creation, and error handling.
    const handleTool = async (queryConfig: Record<string, any> | undefined, apiCall: (gmail: gmail_v1.Gmail) => Promise<any>) => {
      try {
        const oauth2Client = queryConfig ? createOAuth2Client(queryConfig) : defaultOAuth2Client
        if (!oauth2Client) throw new Error('OAuth2 client could not be created, please check your credentials')
    
        const credentialsAreValid = await validateCredentials(oauth2Client)
        if (!credentialsAreValid) throw new Error('OAuth2 credentials are invalid, please re-authenticate')
    
        const gmailClient = queryConfig ? google.gmail({ version: 'v1', auth: oauth2Client }) : defaultGmailClient
        if (!gmailClient) throw new Error('Gmail client could not be created, please check your credentials')
    
        const result = await apiCall(gmailClient)
        return result
      } catch (error: any) {
        return `Tool execution failed: ${error.message}`
      }
    }
  • Shared helper 'formatResponse' used to format the API response as MCP content.
    const formatResponse = (response: any) => ({ content: [{ type: "text", text: JSON.stringify(response) }] })
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 states the tool stops notifications, which implies a mutation, but doesn't clarify permissions needed, side effects (e.g., whether it affects other users), or error conditions. This is a significant gap for a mutation tool with zero annotation coverage.

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 that conveys the core purpose without unnecessary words. It's front-loaded with the main action, making it easy to parse and understand quickly, with zero waste.

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?

Given the tool has no parameters, no output schema, and no annotations, the description adequately covers the basic purpose. However, as a mutation tool, it lacks details on behavioral aspects like permissions or effects, leaving it minimally viable but with clear gaps for agent 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 input schema has 0 parameters with 100% description coverage, so the schema fully documents the lack of parameters. The description doesn't need to add parameter details, and it correctly implies no inputs are required by not mentioning any, earning a baseline score above 3 for appropriate handling.

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'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'watch_mailbox', but the verb 'Stop' implies it's the counterpart to a watch operation.

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 by referencing 'push notifications' and 'user mailbox', suggesting it should be used when notifications need to be disabled. However, it doesn't specify when to use this versus alternatives or mention prerequisites like needing an active watch to stop, leaving some ambiguity.

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

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