Skip to main content
Glama
Praket7

mastercam-mcp

by Praket7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_wcs

Read-onlyIdempotent

Retrieve the active work coordinate system in Mastercam to confirm the current WCS setup. This tool provides the active WCS without modifying the session.

Instructions

Report the active work coordinate system

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNo
liveNo
toolYes
errorNo
receiptNo
documentRevisionNo
operationFingerprintNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 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"
-}
    • 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": {},
+    "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

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds no further behavioral context beyond the fact that it reports current state, which is sufficient given the annotation coverage.

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 concise sentence with no filler. It immediately communicates the tool's purpose and contains no redundant information.

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?

With no parameters, full annotation coverage, and an output schema present, the description is complete for an agent to understand what this tool does and invoke it correctly. No additional context is necessary.

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 and schema coverage is 100%, so there are no parameter semantics for the description to clarify. The baseline of 4 for no-parameter tools applies.

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 ('active work coordinate system'). This clearly distinguishes the tool from siblings like get_machine_context or get_programming_context, whose scopes are different.

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?

There is no guidance on when to use this tool versus alternatives such as get_machine_context or get_active_part. The intended use is only implied by the name and description, not explicitly stated.

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