Skip to main content
Glama
eva-wanxin-git

Windows Automation MCP Server

maximize_window

Maximizes a window to full screen using its title. This tool helps users quickly expand windows for better visibility and workspace management.

Instructions

最大化窗口

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes窗口标题

Implementation Reference

  • The handler function that implements the logic for the 'maximize_window' tool. It currently returns a placeholder message indicating the feature is under development.
    async maximizeWindow(title) {
      try {
        // 这个需要使用 Windows API,暂时返回提示
        return { success: false, message: '功能开发中,建议使用 activate_window 后手动最大化' };
      } catch (error) {
        return { success: false, error: error.message };
      }
    }
  • The input schema definition for the 'maximize_window' tool, including name, description, and required 'title' parameter.
    {
      name: 'maximize_window',
      description: '最大化窗口',
      inputSchema: {
        type: 'object',
        properties: {
          title: { type: 'string', description: '窗口标题' },
        },
        required: ['title'],
      },
    },
  • The switch case in executeTool method that registers and dispatches the 'maximize_window' tool call to the handler.
    case 'maximize_window':
      return await this.maximizeWindow(args.title);
  • The canHandle method includes 'maximize_window' in the list of supported tools.
      const tools = ['list_windows', 'get_active_window', 'activate_window', 
                     'close_window', 'minimize_window', 'maximize_window'];
      return tools.includes(toolName);
    }
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. It mentions maximizing a window but doesn't disclose behavioral traits like whether it requires a window to be active, what happens if the window is already maximized, or if it affects other windows. This leaves significant gaps in understanding the tool's behavior.

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 phrase '最大化窗口', which is extremely concise and front-loaded with the core action. There is no wasted text, making it efficient for quick understanding.

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's complexity (a window operation with no annotations and no output schema), the description is incomplete. It doesn't explain what happens on success or failure, return values, or error conditions. For a tool that interacts with system windows, more context is needed to use it effectively.

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%, with the parameter 'title' documented as '窗口标题' (window title). The description adds no additional meaning beyond the schema, such as examples or constraints. Since the schema fully covers the parameter, a baseline score of 3 is appropriate.

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 '最大化窗口' (maximize window) states a clear verb ('maximize') and resource ('window'), but it's vague about what type of window (e.g., application window, browser window) and doesn't distinguish from sibling tools like 'activate_window' or 'minimize_window'. It provides basic purpose but lacks specificity.

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 like 'activate_window' or 'minimize_window', or prerequisites such as needing an existing window. The description only states the action without context, leaving usage unclear.

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/eva-wanxin-git/windows-automation-mcp'

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