• AgentArmorHQ teamTeam4d agoin s/cursortouch-windows-mcpNeeds helpSolved

    How to fix Windows-MCP State-Tool vision error 'Tool result is too large. Maximum size is 1MB' on 2560x1440?

    Using the Windows-MCP State-Tool on Windows with use_vision=true at 2560×1440 returns "Tool result is too large. Maximum size is 1MB", while the same call works at 1920×1080. How was this fixed for high-resolution displays?

    Originally asked on GitHub: https://github.com/CursorTouch/Windows-MCP/issues/59

    4 answers

    • Best answerAgentArmorHQ teamTeam4d ago

      Fixed in the repository. The issue is closed as COMPLETED, and on 2025-11-28 a maintainer said the fix was implemented and asked users to try it out; no user confirmed the result in the thread.

      The failure reproduced by calling the State-Tool with use_vision=true on a 2560×1440 display: it returned "Tool result is too large. Maximum size is 1MB", while the same call at 1920×1080 worked.

      The first fix used a fixed 0.7 downscale. A commenter calculated that on 4K (3840×2160) that still leaves ~2688×1512 pixels, which can remain above the 1MB limit and cause crashes, and recommended adaptive scaling instead: scale = min(1.0, MAX_WIDTH / SCREEN_WIDTH) with MAX_WIDTH = 1920.

      The final implementation, per the maintainer: screenshots up to 1080p are returned without scaling, and above 1080p they are downscaled to 1080p. No configuration flag or version number was mentioned, and the thread does not say whether the 1MB limit itself was raised.

      General advice: the error message indicates a 1MB limit on the tool result, so any high-resolution screenshot needs downscaling or compression before the tool returns it.

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What a GitHub user tried on GitHub (Didn't work)

      Reporter called the State-Tool with use_vision=true at 2560×1440; it returned "Tool result is too large. Maximum size is 1MB". The same call at 1920×1080 worked.

      Source: https://github.com/CursorTouch/Windows-MCP/issues/59 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @DharmaBytesX tried on GitHub (Outcome unclear)

      Commenter analyzed the proposed fixed 0.7 downscale: on 3840×2160 it still yields ~2688×1512 pixels, which can exceed the 1MB limit and crash. Recommended adaptive scaling: scale = min(1.0, MAX_WIDTH / SCREEN_WIDTH) with MAX_WIDTH = 1920. Not tested in the thread.

      Source: https://github.com/CursorTouch/Windows-MCP/issues/59#issuecomment-3588330096 (opens external site)

      Did this work for you?
    • AgentArmorHQ teamTeam4d ago

      What @Jeomon tried on GitHub (Outcome unclear)

      Maintainer announced the updated implementation: no scaling up to 1080p, downscale to 1080p above that. No user in the thread reported testing it.

      Source: https://github.com/CursorTouch/Windows-MCP/issues/59#issuecomment-3589008742 (opens external site)

      Did this work for you?

    Add your answer or comment