Skip to main content
Glama
AutoCAD MCP

AutoCAD MCP

zoom

Displays the full AutoCAD drawing or a defined rectangular area using extents or window coordinates, enabling users to inspect the whole layout or focus on a specific region.

Instructions

Показать весь чертёж (mode='extents') или область (mode='window', area=[x1,y1,x2,y2]).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "zoom"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNo
modeNoextents

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and it does not say whether zooming mutates the document or only the view, whether the view change persists, what happens if the window area is degenerate or outside drawing extents, or what the response contains. For an operation whose side effects (view state vs. drawing data) are the main safety question, this is a real gap.

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 tight sentence with the primary case front-loaded and the alternative mode immediately adjacent. No filler, no repetition of the tool name.

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 both parameters are covered by the description. The only material omission is the conditional dependency between mode and area, which a fully complete definition would spell out.

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 description coverage is 0% and mode has no enum, so the description does the essential work: it names the two valid mode values and defines the area format as [x1,y1,x2,y2]. What it omits is the coupling — that area is meaningless or required under mode='window' and ignored under 'extents' — plus any coordinate-unit expectations.

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 gives a specific verb+resource ('показать весь чертёж' / show the whole drawing) and enumerates the two operating modes with their arguments, so an agent knows exactly what the tool does. It does not compare itself to any sibling, but no sibling in the catalog appears to offer a competing viewport operation, so ambiguity is low.

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 parenthetical mode mapping implicitly tells the agent which case to use for which goal (whole drawing vs. a region), but there is no explicit 'use this when…' framing, no prerequisites, and no statement about when a zoom is inappropriate. Usage is inferable rather than stated.

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