mastercam-mcp

by Praket7

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

capture_view

Read-onlyIdempotent

Capture a bounded view image from the Mastercam graphics window to share or document the current CAD/CAM session.

Instructions

Capture a bounded view image of the Mastercam graphics window

Input Schema

TableJSON Schema

Name	Required	Default
`width`	No
`format`	No	png
`height`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`live`	No
`tool`	Yes
`error`	No
`receipt`	No
`documentRevision`	No
`operationFingerprint`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv0.3.0Sep 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / properties / confirmed

Removed value: -{
-  "type": "boolean"
-}

removedInput schema / properties / dryRun

Removed value: -{
-  "type": "boolean"
-}

removedInput schema / properties / feed

Removed value: -{
-  "type": "number"
-}

addedInput schema / properties / format

Added value: +{
+  "default": "png",
+  "enum": [
+    "png",
+    "jpeg"
+  ],
+  "type": "string"
+}

addedInput schema / properties / height

Added value: +{
+  "default": 768,
+  "maximum": 1080,
+  "minimum": 64,
+  "type": "integer"
+}

removedInput schema / properties / name

Removed value: -{
-  "type": "string"
-}

removedInput schema / properties / operationId
```
Removed value: -{}
```

removedInput schema / properties / operationIds

Removed value: -{
-  "items": {},
-  "type": "array"
-}

removedInput schema / properties / outputPath
```
Removed value: -{
-  "type": "string"
-}
```

removedInput schema / properties / speed

Removed value: -{
-  "type": "number"
-}

removedInput schema / properties / toolId
```
Removed value: -{}
```

addedInput schema / properties / width

Added value: +{
+  "default": 1024,
+  "maximum": 1920,
+  "minimum": 64,
+  "type": "integer"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {},
+    "documentRevision": {
+      "type": "string"
+    },
+    "error": {
+      "additionalProperties": false,
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        },
+        "remediation": {
+          "type": "string"
+        },
+        "retryable": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "live": {
+      "type": "boolean"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "operationFingerprint": {
+      "type": "string"
+    },
+    "receipt": {},
+    "tool": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}

First observedv0.1.0Sep 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context, such as how the image is returned or whether it is saved to disk. Since annotations cover the key behaviors, a score of 3 is appropriate—consistent but not enriching.

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 no extraneous words. It states the core action and target directly, achieving maximum efficiency.

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?

The tool is simple with no required parameters and an output schema present, so the return format is presumably covered by the schema. The description adequately conveys the primary purpose. Minor ambiguity around 'bounded' and the exact context of the graphics window exists, but given the low complexity and existing annotations, it is sufficiently complete.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for parameter meaning. It does not mention width, height, or format at all. Although the schema provides defaults, enums, and bounds, the description adds zero value to parameter semantics. For a low-coverage case, this is a significant gap.

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 description clearly states the action (capture) and the resource (bounded view image of the Mastercam graphics window). It is specific and distinguishes itself from the sibling tools, which are mostly about operations, toolpaths, and analysis. There is no ambiguity about what this tool does.

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?

No explicit guidance on when to use this tool versus alternatives is given. However, the tool's function is unique among siblings, so the context is implied. The description does not mention when not to use it or any prerequisites, leaving the agent to infer usage from the purpose alone.

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

Deploy Server