Skip to main content
Glama
itrimble

Moom MCP Server

by itrimble

list_layouts

Retrieve saved window layouts for Moom on macOS to manage desktop organization and window positioning.

Instructions

List all saved Moom layouts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'list_layouts' tool. It executes an AppleScript command to list all Moom layouts, parses the result, and returns a JSON-formatted list or error message.
    async listLayouts() {
      const script = `
        tell application "Moom"
          list of layouts
        end tell
      `;
      
      try {
        const result = await this.runAppleScript(script);
        const layouts = result.split(', ').map(name => name.trim());
        
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify({
                layouts: layouts,
                count: layouts.length
              }, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error listing layouts: ${error.message}`,
            },
          ],
        };
      }
    }
  • src/index.js:128-135 (registration)
    Registration of the 'list_layouts' tool in the ListToolsRequestSchema response, including name, description, and empty input schema.
    {
      name: 'list_layouts',
      description: 'List all saved Moom layouts',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema definition for the 'list_layouts' tool, which requires no parameters (empty properties).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • src/index.js:217-218 (registration)
    Dispatch/registration in the CallToolRequestSchema switch statement that maps the tool name to its handler method.
    case 'list_layouts':
      return await this.listLayouts();
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 what the tool does but doesn't describe how it behaves—such as whether it returns a simple list or structured data, if there are any rate limits, or if it requires specific permissions. This leaves significant gaps for an agent to understand the operation fully.

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 directly states the tool's purpose without any fluff. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, and there's no wasted verbiage.

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 simplicity (0 parameters, no annotations, no output schema), the description is adequate as a basic overview. However, it lacks details on return values or behavioral traits, which would help an agent use it effectively. Without an output schema, the description should ideally hint at what 'list' entails, but it doesn't, leaving some context missing.

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% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is applied since the schema fully covers the absence of parameters, and the description doesn't introduce confusion.

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 verb ('List') and resource ('saved Moom layouts'), making the purpose unambiguous. It distinguishes from siblings like 'activate_layout' or 'save_current_layout' by focusing on retrieval rather than modification. However, it doesn't specify if this includes all layout types or just certain categories, which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't clarify if this should be used before 'activate_layout' to see available options, or if it's the primary way to discover layouts versus checking 'show_moom_menu'. The description lacks any context about prerequisites or typical workflows.

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