Skip to main content
Glama
itrimble

Moom MCP Server

by itrimble

create_custom_grid_layout

Define custom window grid layouts for high-resolution displays by specifying columns and rows, enabling precise window arrangement on macOS.

Instructions

Create a custom grid layout (e.g., 3x2, 4x3) for high-res displays

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layoutNameYesName for the grid layout
columnsYesNumber of columns in the grid
rowsYesNumber of rows in the grid

Implementation Reference

  • The main handler function for the 'create_custom_grid_layout' tool. It executes an AppleScript to display a notification as a placeholder implementation, noting that the full grid layout feature is coming soon.
    async createCustomGridLayout(layoutName, columns, rows) {
      const script = `
        tell application "Moom"
          -- This would require Moom's grid API or custom positioning
          -- For now, we'll create a notification
          display notification "Grid layout ${columns}x${rows} would be created here" with title "${layoutName}"
        end tell
      `;
    
      try {
        await this.runAppleScript(script);
        return {
          content: [{
            type: 'text',
            text: `Grid layout feature coming soon. For now, use Moom's built-in grid with ${columns}x${rows} dimensions.`
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: `Error: ${error.message}`
          }]
        };
      }
    }
  • Input schema defining the parameters for the 'create_custom_grid_layout' tool: layoutName (string), columns (integer), rows (integer).
    inputSchema: {
      type: 'object',
      properties: {
        layoutName: {
          type: 'string',
          description: 'Name for the grid layout',
        },
        columns: {
          type: 'integer',
          description: 'Number of columns in the grid',
        },
        rows: {
          type: 'integer',
          description: 'Number of rows in the grid',
        },
      },
      required: ['layoutName', 'columns', 'rows'],
    },
  • src/index.js:106-127 (registration)
    Tool registration in the ListTools response, including name, description, and input schema.
    {
      name: 'create_custom_grid_layout',
      description: 'Create a custom grid layout (e.g., 3x2, 4x3) for high-res displays',
      inputSchema: {
        type: 'object',
        properties: {
          layoutName: {
            type: 'string',
            description: 'Name for the grid layout',
          },
          columns: {
            type: 'integer',
            description: 'Number of columns in the grid',
          },
          rows: {
            type: 'integer',
            description: 'Number of rows in the grid',
          },
        },
        required: ['layoutName', 'columns', 'rows'],
      },
    },
  • src/index.js:221-222 (registration)
    Dispatch case in the CallToolRequest handler that routes to the createCustomGridLayout method.
    case 'create_custom_grid_layout':
      return await this.createCustomGridLayout(args.layoutName, args.columns, args.rows);
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 the tool creates a layout but doesn't cover critical aspects like whether this requires specific permissions, if it overwrites existing layouts, what happens on success/failure, or any rate limits. For a creation tool with zero annotation coverage, this is a significant gap in transparency.

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 front-loads the core purpose ('Create a custom grid layout') and includes helpful examples and context without any wasted words. It's appropriately sized for the tool's complexity.

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 tool creates a layout (a mutation operation) with no annotations and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., permissions, side effects), return values, or error handling, which are crucial for an agent to use this tool effectively in context with siblings.

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 input schema already documents all three parameters (layoutName, columns, rows) with clear descriptions. The description adds minimal value beyond the schema by implying the grid dimensions (e.g., '3x2') but doesn't provide additional syntax, constraints, or usage details for the parameters.

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 ('Create') and resource ('custom grid layout'), with specific examples like '3x2, 4x3' and context about 'high-res displays'. However, it doesn't explicitly distinguish this tool from sibling tools like 'create_quad_layout' or 'save_current_layout', which might also involve layout creation or management.

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. It doesn't mention sibling tools like 'create_quad_layout' (which might create a specific type of layout) or 'save_current_layout' (which might save an existing layout), leaving the agent without clear usage context or exclusions.

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