Skip to main content
Glama
Sign In
Touchpoint

Touchpoint

by Touchpoint-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

move_window

Move a window to a new screen position by specifying its ID and top-left corner coordinates.

Instructions

Move a window to a new screen position.

Use windows() to find the window ID first.

Args:
    window_id: The window ID to move.
    x: New horizontal position of the top-left corner.
    y: New vertical position of the top-left corner.

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>",
      "x": "<x>",
      "y": "<y>"
    },
    "name": "move_window"
  }
}

Input Schema

NameRequiredDescriptionDefault
window_idYes
xYes
yYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

B3.3/5.0
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 only states the action without detailing side effects, permissions needed, or behavior on failure. For a simple tool, minimal transparency is given.

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 extremely concise at three short sentences plus argument explanations. The main purpose is front-loaded in the first sentence, and there is no unnecessary information.

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?

The tool is simple with 3 parameters and no nested objects. The description covers prerequisites (finding window ID) but omits coordinate system details, error handling, or any output schema explanation. It is partially complete for a basic tool.

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?

The 'Args' section adds meaning to parameters beyond their names, e.g., explaining x and y as new top-left corner positions. However, it lacks details like coordinate system (screen vs. window), units, or bounds, leaving some ambiguity. With 0% schema description coverage, this is adequate but not comprehensive.

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?

Clearly states 'Move a window to a new screen position' with a specific verb and resource. However, it does not specify the coordinate system (e.g., absolute screen coordinates), which would improve precision.

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?

Provides a prerequisite (use windows() to find window ID) but lacks guidance on when to use this tool versus alternatives like resize_window or focus. No exclusions or when-not-to-use are mentioned.

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

Deploy Server

Other Tools