mastercam-mcp

Overview Schema Source Related Servers Discussions Admin

mastercam_status

Read-onlyIdempotent

Check whether Mastercam is connected and identify the active adapter to confirm the integration is ready for CAD/CAM operations.

Instructions

Report live Mastercam connection status and adapter identity

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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.

Changed11 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"
-}

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: -{}
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "additionalProperties": false,
+      "properties": {
+        "adapter": {
+          "type": "string"
+        },
+        "backend": {
+          "type": "string"
+        },
+        "connected": {
+          "type": "boolean"
+        },
+        "mastercamVersion": {
+          "type": "string"
+        },
+        "protocolVersion": {
+          "type": "number"
+        },
+        "runtime": {
+          "type": "string"
+        },
+        "stageBProgrammingContextProbe": {
+          "additionalProperties": false,
+          "properties": {
+            "getOperationsFound": {
+              "type": "boolean"
+            },
+            "getOperationsReturnType": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "notes": {
+              "items": {
+                "type": "string"
+              },
+              "type": "array"
+            },
+            "searchManagerAssembly": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "searchManagerFound": {
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "searchManagerFound",
+            "getOperationsFound",
+            "notes"
+          ],
+          "type": "object"
+        },
+        "stageBReadsEnabled": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "connected",
+        "backend",
+        "adapter",
+        "runtime",
+        "mastercamVersion",
+        "protocolVersion"
+      ],
+      "type": "object"
+    },
+    "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

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the 'live' qualifier, which conveys that the status is real-time rather than cached, and specifies that adapter identity is part of the response, providing behavioral context beyond the annotations.

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?

The description is a single, front-loaded sentence that starts with the action verb and states the core purpose without filler. Every word contributes to understanding what the tool does.

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 zero-parameter read-only status tool with a rich output schema present, the description is complete enough. It identifies the tool's purpose and lets the output schema handle return-value details, so nothing critical is missing.

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?

The tool has zero parameters, so there is no parameter burden for the description to carry. Schema description coverage is 100% by default with an empty schema, and the description correctly omits any parameter discussion since none exist.

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 uses a specific verb ('Report') and a specific resource ('live Mastercam connection status and adapter identity'). This clearly distinguishes it from sibling tools like get_version_report or client_setup_check, which target different information.

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 implies the tool is for checking current connection state and adapter identity, but it does not explicitly state when to prefer it over alternatives or when not to use it. Usage is reasonably inferable from the name and purpose, but no exclusions or alternatives are mentioned.

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

Deploy Server