Power CAD MCP

Overview Schema Source Related Servers Discussions Admin

zoom_window

Zoom the CAD viewport to a rectangular window defined by two corner points, enabling targeted inspection of a drawing area.

Instructions

Zoom the view to the window spanned by two corners.

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": {
      "p1": "<p1>",
      "p2": "<p2>"
    },
    "name": "zoom_window"
  }
}

Input Schema

Name	Required	Description	Default
`p1`	Yes	[x, y] or [x, y, z]
`p2`	Yes	[x, y] or [x, y, z]

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds that it zooms the view (not drawing data), which is mildly useful, but it omits reversibility, persistence, and coordinate-system details.

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?

A single front-loaded sentence with zero waste. It states the operation and its defining input in one pass.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. For a simple viewport zoom, the description is adequate, though it could mention viewport-only scope or coordinate system.

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?

Schema coverage is 100% and already documents the coordinate formats. The description adds the semantic role that p1 and p2 are two corners spanning the window, which is meaningfully more than the schema provides.

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?

States a specific verb 'Zoom' and resource 'view to the window spanned by two corners'. It is clear in isolation, but does not name or differentiate from the sibling zoom_extents, so it falls short of a 5.

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 explicit when-to-use guidance, exclusions, or alternative tools are mentioned. The sibling zoom_extents exists but is not referenced, leaving the agent to infer the choice from the tool name alone.

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