Skip to main content
Glama
Praket7

mastercam-mcp

by Praket7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_operation_parameters

Read-onlyIdempotent

Retrieve proven parameters for a specific Mastercam operation by its exact ID, enabling you to verify or reuse machining settings without manual lookup.

Instructions

Retrieve one operation's proven parameters by exact id

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": {
+      "additionalProperties": false,
+      "properties": {
+        "documentRevision": {
+          "type": "string"
+        },
+        "operationId": {
+          "type": "number"
+        },
+        "parameters": {
+          "additionalProperties": {},
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "operationId",
+        "parameters",
+        "documentRevision"
+      ],
+      "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"
+}
  2. First observedv0.1.0

TDQS

B3.4/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, so the safety profile is covered. The description adds the 'proven' qualifier and 'exact id' semantics, suggesting a validated, exact-match lookup, but does not disclose additional behaviors such as error conditions or prerequisites.

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 sentence with no filler words. It front-loads the verb and keeps the key qualifiers ('proven', 'exact id') tight, making it easy to scan.

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 simple one-parameter read operation with rich annotations and an output schema, so the description covers the core invocation semantics. It could be better by mentioning how to obtain the operationId (e.g., from list_operations), but that is more of a usage-guideline gap than a fundamental completeness gap.

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

Parameters3/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 carry the parameter meaning. The phrase 'by exact id' indicates operationId is an exact-match identifier, but it does not explain what an operation ID is or how to obtain it, leaving the parameter semantics only partially clarified.

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 states a specific verb ('retrieve'), resource ('one operation's proven parameters'), and method ('by exact id'). It is clear about what the tool does, but it does not explicitly distinguish it from sibling tools like get_operation or preview_operation_parameters.

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. It does not mention that a user should call this when they need proven parameters for a specific operation, nor does it point to siblings like list_operations or get_operation for finding IDs.

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