multiCAD-mcp-server

Overview Schema Source Related Servers Discussions Admin

manage_view

Control CAD camera viewport, zoom, 3D viewpoint presets, and shading styles; capture screenshots and step undo/redo without modifying drawing entities.

Instructions

Control CAD camera viewport, display zoom, 3D viewpoint presets, and visual shading styles.

Behavior:

Mutation: Modifies interactive viewport display state (zoom factor, center point, view direction, visual style) in the active CAD editor window. Does NOT modify drawing database entities.
Persistence: Viewport changes persist in the active drawing session until manually adjusted or closed.
Side Effects: Refreshes display graphics in active CAD GUI. In screenshot/preview operations, reads screen framebuffer and returns base64 image data.

Usage Guidelines:

When to Use: Call whenever navigating the drawing, zooming to extents (ze), zooming into specific coordinates (zw), switching to 3D axonometric perspectives (preset|iso_sw), changing shading (style|realistic), or stepping through history (undo/redo).
Sibling Routing / Alternatives:
- For creating, configuring, or activating paperspace sheet presentations and architectural viewports, use manage_layouts.
- For launching an interactive web-based canvas viewer for human inspection in the browser, use show_drawing_viewer.
- For exporting vector PDF sheets or SVG files to disk, use export_data.

Shorthand Grammar (one command per line or semicolon-separated):

ze (or zoom_extents): Zoom to fit all drawing entities in viewport.
zw|x1,y1|x2,y2 (or zoom_window): Zoom into rectangular window bounds.
zc|x,y|mag (or zoom_center): Center view on coordinate (x,y) with optional magnification factor.
preset|top|bottom|front|back|left|right|iso_sw|iso_se|iso_ne|iso_nw: Switch 3D or orthographic viewpoint.
style|2d|wireframe|conceptual|realistic|shaded|hidden: Set visual rendering mode.
screenshot / preview: Capture visual raster snapshot of current drawing viewport.
undo|count / redo|count: Step backward or forward in CAD session history (default count: 1).

Parameters:

operations: Shorthand string commands (one per line) or JSON array of operation objects.

Returns: JSON string containing per-operation execution results, success status, and details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`operations`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations provided, the description carries the full burden and does so: it states the mutation is viewport-only and explicitly 'Does NOT modify drawing database entities,' notes persistence until manual adjustment or close, and discloses side effects including the base64 framebuffer return from screenshot/preview. That is exactly the mutation-safety context annotations would otherwise supply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose and organized under clear headers (Behavior, Usage Guidelines, Shorthand Grammar, Parameters, Returns), so it is scannable. It runs long, with some overlap between the Behavior section and the grammar list (e.g., screenshot/preview described twice), but given 0% schema coverage the grammar list is load-bearing rather than filler.

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

Completeness5/5

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

For a one-parameter, command-string tool with no annotations, the description covers purpose, mutation scope, persistence, side effects, invocation grammar, and routing to alternatives. An output schema exists, and the description appropriately limits itself to a one-line Returns note instead of duplicating return structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'operations' parameter, so the description must compensate and does: it documents the accepted string grammar command-by-command (ze, zw|x1,y1|x2,y2, zc|x,y|mag, preset, style, screenshot, undo/redo) including defaults for undo/redo count. This adds far more than the bare 'type: string' schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource+scope: 'Control CAD camera viewport, display zoom, 3D viewpoint presets, and visual shading styles.' The explicit sibling-routing block distinguishes it from manage_layouts, show_drawing_viewer, and export_data, so an agent can select it without opening any schema.

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

Usage Guidelines5/5

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

A dedicated 'When to Use' list enumerates concrete triggers (zooming to extents, switching to axonometric views, changing shading, undo/redo), and 'Sibling Routing / Alternatives' names three alternatives with the condition that selects each. This is explicit when-to-use plus when-not-to-use coverage.

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

Deploy Server