Skip to main content
Glama
Praket7

mastercam-mcp

by Praket7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_toolpath_status

Read-onlyIdempotent

Determine the toolpath status (dirty, current, or unknown) for a Mastercam operation using its operation ID.

Instructions

Report mapped toolpath dirty/current/unknown state for an operation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationIdYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNo
liveNo
toolYes
errorNo
receiptNo
documentRevisionNo
operationFingerprintNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv0.3.0
    • 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"
-}
    • addedInput schema / properties / operationId / maximum
      Added value: +2147483647
    • addedInput schema / properties / operationId / minimum
      Added value: +1
    • addedInput schema / properties / operationId / type
      Added value: +"integer"
    • 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 / required
      Added value: +[
+  "operationId"
+]
    • 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"
+}
  2. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds value by naming the tri-state output (dirty/current/unknown), but it does not explain behavior for unmapped operations or invalid operation IDs. There is no contradiction with 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?

A single, front-loaded sentence with no filler. Every word contributes meaning, and the core state values are stated compactly.

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?

This is a low-complexity tool with one parameter, a rich annotation set, and an output schema. The description sufficiently communicates the tool's purpose and key state vocabulary; the only notable gap is the undefined 'mapped' concept, which is minor given the output schema likely documents the result structure.

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 the undocumented operationId parameter. It only says 'for an operation,' which weakly implies what operationId refers to, but it does not clarify how to obtain it, what 'mapped' means, or how the parameter relates to the reported status.

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

Purpose4/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 clear resource: the dirty/current/unknown state of a mapped toolpath for an operation. It is clear but does not explicitly differentiate itself from siblings like get_dirty_toolpaths, which could appear to overlap.

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

Usage Guidelines2/5

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

The description implies the tool is used when you need toolpath status for a specific operation, but it provides no explicit guidance on when to choose this over get_dirty_toolpaths, get_operation, or other status-related tools. No alternatives or exclusions 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

Other Tools