CADPilot

Overview Schema Source Related Servers Discussions Admin

get_view

Read-onlyIdempotent

Capture a FreeCAD document view as a PNG and return its saved path, enabling visual checks of model geometry and assemblies.

Instructions

Capture one document's view and return the saved PNG's path.

Costly in context: reserve it for visual checks; prefer get_objects or measure_geometry for numbers. Without width/height the long edge is capped at 384 px.

Args:
    view_name: Camera view, one of the nine names.
    width/height: Pixel size; a smaller image saves context.
    focus_object: Fit this object; the default frames everything.
    doc_name: Frame this document; another agent may have switched the foreground tab.

Input Schema

Name	Required	Description	Default
`width`	No
`height`	No
`doc_name`	No
`view_name`	Yes
`focus_object`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.7.7Oct 7, 2026

addedInput schema / properties / doc_name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Doc Name"
+}

changedInput schema / properties / height / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 8192,
+    "minimum": 16,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

changedInput schema / properties / width / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 8192,
+    "minimum": 16,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / $defs / ImageContent

Removed value: -{
-  "additionalProperties": true,
-  "description": "Image content for a message.",
-  "properties": {
-    "_meta": {
-      "anyOf": [
-        {
-          "additionalProperties": true,
-          "type": "object"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null,
-      "title": "Meta"
-    },
-    "annotations": {
-      "anyOf": [
-        {
-          "$ref": "#/$defs/Annotations"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": null
-    },
-    "data": {
-      "title": "Data",
-      "type": "string"
-    },
-    "mimeType": {
-      "title": "Mimetype",
-      "type": "string"
-    },
-    "type": {
-      "const": "image",
-      "title": "Type",
-      "type": "string"
-    }
-  },
-  "required": [
-    "type",
-    "data",
-    "mimeType"
-  ],
-  "title": "ImageContent",
-  "type": "object"
-}

addedOutput schema / properties / result / items / $ref
```
Added value: +"#/$defs/TextContent"
```

removedOutput schema / properties / result / items / anyOf

Removed value: -[
-  {
-    "$ref": "#/$defs/ImageContent"
-  },
-  {
-    "$ref": "#/$defs/TextContent"
-  }
-]

First observedv0.4.0Jul 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds genuine behavioral context beyond that: the tool is context-costly, returns a saved PNG path, and caps the long edge at 384 px when width/height are omitted. It stops short of describing session/GUI prerequisites for the capture.

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 purpose, then the cost caveat, then a compact Args block; each sentence carries information. The Args list slightly overlaps the schema, but with 0% schema coverage that redundancy is doing necessary work.

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, return-value detail is not required, and the safety/behavioral burden is largely carried by annotations. Combined with full parameter documentation and the cost warning, an agent has what it needs to call it correctly; only GUI/session preconditions remain unstated.

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 0%, so the description carries the full burden, and it documents all five parameters: view_name (one of nine), width/height (pixel size with a context-saving rationale), focus_object (fit behavior), and doc_name (foreground-tab hazard). The only gap is that enum membership and min/max bounds live in the schema rather than being restated.

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?

States a specific verb and resource ('Capture one document's view') and names the concrete return value ('the saved PNG's path'). It also differentiates from siblings by pointing to get_objects and measure_geometry for numeric needs, so an agent can distinguish it without opening schemas.

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?

Explicitly says when to use it ('reserve it for visual checks') and when not to ('prefer get_objects or measure_geometry for numbers'), naming the alternatives. The doc_name note also warns of a real hazard (another agent may have switched the foreground tab).

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