FreeCAD Tutor MCP

Overview Schema Source Related Servers Discussions Admin

get_view

Read-onlyIdempotent

Capture the FreeCAD 3D viewport or full application window as a PNG, optionally specifying view angle, image size, and an object to focus before taking the screenshot.

Instructions

Capture the 3D viewport (capture_scope='viewport') or full FreeCAD window ('window') as PNG.

Args: view_name: 'Current', 'Isometric', 'Front', 'Top', 'Right', 'Back', 'Left', 'Bottom', 'Dimetric', or 'Trimetric'. width: Optional explicit image width (auto-scaled <=1024px viewport / <=1280px window). height: Optional explicit image height. focus_object: Optional object name to zoom/fit before capturing. capture_scope: 'viewport' for clean 3D render, or 'window' to include Task panels, Combo View, and dialogs.

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": "get_view"
  }
}

Input Schema

Name	Required	Default
`width`	No
`height`	No
`view_name`	No	Current
`focus_object`	No
`capture_scope`	No	viewport

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description doesn't need to repeat safety. It instead adds useful operational detail the annotations lack: automatic downscaling limits (<=1024px viewport / <=1280px window) and the pre-capture zoom/fit performed by focus_object.

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?

The core behavior is front-loaded in one sentence before the Args block, and each line earns its place by documenting a parameter the schema leaves bare. The docstring-style list repeats the parameter names, but that repetition aids scanning rather than bloating the text.

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?

With an output schema present, the description rightly omits return-value details and focuses on capture modes, scaling behavior, and parameter values. For a five-parameter, zero-coverage schema this covers everything an agent needs to call it correctly, short only of edge-case syntax notes.

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 view_name has no enum, so the description carries the full burden — and it largely does, enumerating all ten valid view names and the two capture_scope values, plus the scaling caps for width/height. Minor gaps remain, e.g. case sensitivity of view_name and what an empty focus_object means.

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?

The opening sentence uses a specific verb and resource — capture the 3D viewport or full FreeCAD window as PNG — and immediately distinguishes the two capture modes. An agent can tell this is a screenshot tool rather than a view-setting tool like set_view.

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 explains when to pick each capture_scope value ('viewport' for a clean 3D render vs 'window' to include Task panels, Combo View and dialogs), which is genuine selection guidance. It gives no guidance on when to use this tool versus siblings such as set_view or get_selection, nor any stated prerequisites.

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

Deploy Server