Skip to main content
Glama
Praket7

mastercam-mcp

by Praket7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_selection

Read-onlyIdempotent

Retrieves and reports the list of operations currently selected in the active Mastercam session, providing immediate visibility into the user's selection for downstream workflows.

Instructions

Report currently selected operations

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is established. The description adds the scope (operations) but does not disclose additional behaviors such as whether the selection is session-persistent, how empty selections are handled, or the exact return format (though output schema exists). Given the annotations, a 3 is appropriate.

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 that is front-loaded and contains no filler. It efficiently communicates the tool's core purpose.

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?

For a tool with no parameters and an output schema, the description is adequate for an agent to understand what it does. The lack of usage guidance is a minor gap given the simplicity, but the description is otherwise complete.

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?

There are zero parameters, so the schema fully covers parameter semantics. The baseline for 0 params is 4, and the description adds no redundant parameter information.

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 the specific verb 'Report' and the resource 'currently selected operations', making the tool's purpose clear. It does not explicitly distinguish itself from the sibling tool get_selected_entities, but the resource specificity (operations vs. entities) provides implicit differentiation.

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 like get_selected_entities or list_operations. The description does not mention any selection prerequisites, typical scenarios, or exclusions, leaving the agent to infer usage context.

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