Skip to main content
Glama
itrimble

Moom MCP Server

by itrimble

save_current_layout

Save your current window arrangement as a named layout in Moom for macOS, enabling quick restoration of your preferred workspace setup.

Instructions

Save the current window arrangement as a new Moom layout

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layoutNameYesName for the new layout

Implementation Reference

  • The handler function that saves the current window arrangement as a new Moom layout using AppleScript.
    async saveCurrentLayout(layoutName) {
      // Use AppleScript to save layout
      const script = `
        tell application "Moom"
          save layout and replace "${layoutName}"
        end tell
      `;
      
      try {
        await this.runAppleScript(script);
        return {
          content: [
            {
              type: 'text',
              text: `Successfully saved layout: ${layoutName}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error saving layout: ${error.message}`,
            },
          ],
        };
      }
    }
  • Input schema defining the required 'layoutName' parameter for the tool.
    inputSchema: {
      type: 'object',
      properties: {
        layoutName: {
          type: 'string',
          description: 'Name for the new layout',
        },
      },
      required: ['layoutName'],
    },        },
  • src/index.js:211-212 (registration)
    Registration of the tool in the CallToolRequestHandler switch statement, dispatching to the handler method.
    case 'save_current_layout':
      return await this.saveCurrentLayout(args.layoutName);
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 saves a layout but doesn't describe what happens after saving (e.g., whether it's stored persistently, if it overwrites existing layouts, or what permissions are required). For a mutation tool with zero annotation coverage, this is a significant gap in behavioral 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, well-structured sentence that efficiently conveys the core purpose without any wasted words. It's front-loaded with the main action and resource, making it easy for an agent to parse quickly.

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's moderate complexity (a mutation with one parameter) and no annotations or output schema, the description is minimally adequate. It states what the tool does but lacks details on behavioral traits, usage context, or return values, leaving gaps that could hinder an agent's ability to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the single parameter 'layoutName' with its description. The description doesn't add any meaning beyond what the schema provides (e.g., no format constraints or examples). Baseline 3 is appropriate when the schema does the heavy lifting.

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 states the specific action ('Save the current window arrangement') and the resource ('as a new Moom layout'), distinguishing it from siblings like 'activate_layout' or 'list_layouts'. It uses precise language that leaves no ambiguity about what the tool does.

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 provides no guidance on when to use this tool versus alternatives like 'create_custom_grid_layout' or 'create_quad_layout'. It doesn't mention prerequisites (e.g., needing windows to be arranged first) or exclusions, leaving the agent to infer usage context from the tool name alone.

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