Check current Mastercam session capabilities to verify supported operations and tool parameters for safe dry runs.
Mastercam mastercam capabilities
| Name | Required | Description | Default |
|---|---|---|---|
| feed | No | ||
| name | No | ||
| speed | No | ||
| dryRun | No | ||
| toolId | No | ||
| confirmed | No | ||
| outputPath | No | ||
| operationId | No | ||
| operationIds | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided and the description discloses no behavioral traits whatsoever. An agent cannot determine whether this tool reads state, mutates data, runs simulations, or has side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The text is extremely short, but this is under-specification rather than useful conciseness. It contains no front-loaded meaning and no sentence earns its place because none provides actionable information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 9 undocumented parameters, no output schema, no annotations, and a complex CAM domain, this description is completely inadequate for an agent to select or invoke the tool correctly. It explains neither what the tool does nor what the parameters control.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does nothing to explain any of the 9 parameters such as feed, speed, dryRun, operationIds, or outputPath. The agent has no semantic grounding for any input.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Mastercam mastercam capabilities' is a tautology that restates the tool name and gives no verb, resource, or concrete action. It does not distinguish this tool from any of the 25 siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 or when to prefer an alternative. The description provides zero context about use cases, prerequisites, or relationships to sibling operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.