Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

update_scad_parameter

Read-only

Update a named numeric parameter in OpenSCAD code without regenerating the model, preserving comments and formatting; derived parameters are refused with guidance to change their source parameters.

Instructions

Update a parameter value in OpenSCAD code.

        Finds the named variable declaration and replaces its value,
        preserving comments and formatting. Use this to tweak dimensions
        without regenerating the entire model. A derived parameter is
        refused with a message naming its formula and the parameters to
        change instead.

        Args:
            scad_code: OpenSCAD source code string.
            parameter_name: Name of the variable to update.
            new_value: New numeric value for the parameter.

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": {
      "scad_code": "<scad_code>",
      "parameter_name": "<parameter_name>",
      "new_value": "<new_value>"
    },
    "name": "update_scad_parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_valueYesNew numeric value for the parameter.
scad_codeYesOpenSCAD source code string.
parameter_nameYesName of the variable to update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.5.1
    • addedInput schema / properties / new_value / description
      Added value: +"New numeric value for the parameter."
    • addedInput schema / properties / parameter_name / description
      Added value: +"Name of the variable to update."
    • addedInput schema / properties / scad_code / description
      Added value: +"OpenSCAD source code string."
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the readOnly/destructive annotations, it discloses that comments and formatting are preserved and that a derived parameter is refused with a message naming its formula and the parameters to change instead. That is genuinely useful behavior an agent could not infer from the schema. It does not say what happens when the named parameter is absent or what exactly is returned.

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?

The main body is front-loaded and efficient: purpose, mechanism, use case, then the derived-parameter exception. The trailing Args block duplicates the input schema and is wasted text, which keeps it from a 5.

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 three-parameter string-transform tool with annotations covering safety and no output schema, the description covers purpose, preservation behavior, and the key refusal path. Minor gaps remain around the not-found case and the returned code, but nothing essential is missing.

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 100%, so the three parameters are already documented. The Args block in the description restates the schema fields near-verbatim and adds no format, constraint, or expression-syntax guidance (for example whether new_value must be a bare number rather than a formula).

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 names a specific verb and resource ("Update a parameter value in OpenSCAD code") and describes the mechanism (finds the named variable declaration and replaces its value), which separates it from siblings like modify_scad_module or insert_into_scad. It doesn't explicitly name an alternative tool, so it stops short of the top score.

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

Usage Guidelines4/5

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

"Use this to tweak dimensions without regenerating the entire model" gives a clear use case and implicitly excludes full-regeneration or structural-edit tools. There is no explicit when-not-to-use guidance or named alternative, so it is clear context rather than full routing.

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