mastercam-mcp

by Praket7

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

estimate_cycle_time

Read-onlyIdempotent

Estimate cycle time for selected operations to plan machining schedules.

Instructions

Estimate cycle time for selected operations

Input Schema

TableJSON Schema

Name	Required	Description	Default
`operationIds`	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"
-}

removedInput schema / properties / name

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

removedInput schema / properties / operationId
```
Removed value: -{}
```
addedInput schema / properties / operationIds / items / maximum
```
Added value: +2147483647
```
addedInput schema / properties / operationIds / items / minimum
```
Added value: +1
```
addedInput schema / properties / operationIds / items / type
```
Added value: +"integer"
```
addedInput schema / properties / operationIds / maxItems
```
Added value: +1000
```
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"
+}

First observedv0.1.0Sep 8, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no extra behavioral context, such as prerequisites (e.g., requiring an active selection) or how the estimate is derived. It relies entirely on the minimal phrase, which doesn't disclose anything 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 short sentence with zero extraneous words. It is front-loaded with the verb and resource, making it highly concise and structurally efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The presence of an output schema covers return values, and the single-parameter complexity is low. However, the description omits any usage context, such as whether a selection is required, how it relates to 'analyze_cycle_time', or any assumptions about the current part state. For a tool with such minimal description, this is a noticeable gap.

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?

The schema has 0% description coverage for the single parameter 'operationIds', and the description does not elaborate on it. While the parameter name is somewhat self-explanatory (an array of operation IDs), the description doesn't confirm its meaning, format, or constraints, leaving a gap that the schema also fails to fill.

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 ('Estimate') and resource ('cycle time for selected operations'), making the primary function clear. However, it doesn't differentiate from the sibling tool 'analyze_cycle_time', which likely serves a similar purpose, so it's not fully distinctive.

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?

No guidance is provided on when to use this tool versus alternatives like 'analyze_cycle_time' or when not to use it. The description leaves the selection criteria entirely to the agent's inference.

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

Deploy Server