Touchpoint

by Touchpoint-Labs

Overview Schema Source Related Servers Discussions Admin

Python

Local

resize_window

Resize a desktop window to precise pixel dimensions. Provide the window ID, new width, and height to adjust its size.

Instructions

Resize a window.

Use windows() to find the window ID first.

Args:
    window_id: The window ID to resize.
    width: New width in pixels.
    height: New height in pixels.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "window_id": "<window_id>",
      "width": "<width>",
      "height": "<height>"
    },
    "name": "resize_window"
  }
}

Input Schema

Name	Required	Description	Default
`window_id`	Yes
`width`	Yes
`height`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.0Jun 15, 2026

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the burden. It does not disclose any behavioral traits such as side effects, permissions needed, or error conditions. For a simple resize operation, this is adequate but not outstanding.

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 very concise: three lines of text plus parameter list. No unnecessary words, and it front-loads the purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that an output schema exists (not shown but indicated), the description covers the essential info: what it does, parameters with units, and a prerequisite. It does not discuss constraints or return values, but those are handled by the output schema.

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?

With 0% schema description coverage, the description adds value by specifying 'in pixels' for width and height, and clarifying that window_id is the target. This goes beyond the schema titles.

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 'Resize a window' with verb and resource. While it doesn't explicitly differentiate from siblings like move_window or fullscreen_window, the action is distinct enough.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides a helpful prerequisite: use windows() to find the window ID. However, it does not mention when not to use this tool or suggest alternatives among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.