Skip to main content
Glama
itrimble

Moom MCP Server

by itrimble

show_moom_menu

Display the Moom popup menu to access and manage window layout controls on macOS through Claude Desktop.

Instructions

Show the Moom popup menu

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main execution logic for the 'show_moom_menu' tool. It runs an AppleScript that tells System Events to click the Moom menu bar item (menu bar item 1 of menu bar 2), displaying the popup menu. Returns a markdown content block with success or error message.
    async showMoomMenu() {
      const script = `
        tell application "System Events"
          tell process "Moom"
            try
              -- Click on the Moom menu bar icon
              click menu bar item 1 of menu bar 2
              return "Moom menu is now visible"
            on error errMsg
              return "Error showing Moom menu: " & errMsg
            end try
          end tell
        end tell
      `;
    
      try {
        const result = await this.runAppleScript(script);
        return {
          content: [
            {
              type: 'text',
              text: result,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error: ${error.message}`,
            },
          ],
        };
      }
    }
  • src/index.js:74-81 (registration)
    Tool registration in the ListToolsRequestHandler response. Defines the tool name, description, and input schema (empty object since no parameters required).
    {
      name: 'show_moom_menu',
      description: 'Show the Moom popup menu',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Dispatch logic in the CallToolRequestHandler switch statement that routes 'show_moom_menu' tool calls to the showMoomMenu() handler method.
    case 'show_moom_menu':
      return await this.showMoomMenu();
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Show the Moom popup menu,' which implies a read-only or display action, but doesn't clarify if this is a UI interaction, if it blocks other operations, or what happens on failure. For a tool with zero annotation coverage, this is insufficient to inform safe usage.

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 and target, making it easy to parse quickly. Every word earns its place by conveying the essential purpose without redundancy.

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 lack of annotations and output schema, the description is incomplete for effective use. It doesn't explain what the Moom popup menu is, what it displays, or what the expected outcome is (e.g., does it return data or just trigger a UI event?). For a tool in a set with potential UI interactions, more context is needed to understand its role and behavior.

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% (as there are no parameters to describe). The description doesn't need to add parameter details, so it meets the baseline expectation without compensation needed. No points are deducted since there's nothing to document beyond the empty schema.

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 ('Show') and target ('Moom popup menu'), which provides a basic understanding of what the tool does. However, it doesn't specify what the Moom popup menu contains or how it differs from sibling tools like 'trigger_moom_action' or 'activate_layout', leaving the purpose somewhat vague without sibling differentiation.

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?

The description offers no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, such as whether it requires Moom to be running or if it's interactive versus automated. With sibling tools like 'trigger_moom_action' that might overlap, this lack of guidance is a clear gap.

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/itrimble/moom-mcp'

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