cadkit

Overview Schema Source Related Servers Discussions Admin

cad_edit_feature

Edit parameters of existing CAD features by specifying parameter ID and new expression or value. Supports retargeting dimensions to variables without rebuilding.

Instructions

Edit one stored parameter of an existing feature. Give parameterId (e.g. 'depth','radius','length') plus expression (number/#var for a quantity) OR value (enum/bool/string). Retarget a dimension to a #variable without rebuilding.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "documentId": "<documentId>",
      "workspaceId": "<workspaceId>",
      "elementId": "<elementId>",
      "featureId": "<featureId>",
      "parameterId": "<parameterId>"
    },
    "name": "cad_edit_feature"
  }
}

Input Schema

Name	Required	Description	Default
`documentId`	Yes
`workspaceId`	Yes
`elementId`	Yes
`featureId`	Yes
`parameterId`	Yes
`expression`	No
`value`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Jun 24, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, so description must convey behavioral traits. Describes mutation (edit) but omits side effects, reversibility, error handling, or required permissions. Only basic operation description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, concise and direct. First sentence states action and inputs, second highlights key capability. No fluff, though slightly dense and could be clearer about mutual exclusivity of expression/value.

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

Completeness2/5

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

No output schema and no description of return values, prerequisites, or side effects. For a tool with 7 parameters, the description is incomplete, focusing only on core editing functionality.

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 coverage is 0%, so description must compensate. It explains parameterId with examples and distinguishes expression vs value. However, it does not describe documentId, workspaceId, elementId, or featureId, leaving significant gaps. Adds some value but incomplete.

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?

Clearly states verb 'edit' and resource 'stored parameter of an existing feature'. Provides specific examples of parameterId (depth, radius, length) and distinguishes from siblings like cad_set_variable by mentioning retargeting to a variable without rebuilding.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for editing a single feature parameter and retargeting to a variable, but lacks explicit when/when-not guidance or contrast with sibling tools like cad_set_variable or cad_extrude. No prerequisites or exclusions mentioned.

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