Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

parse_scad_parameters

Read-only

Discover which OpenSCAD dimensions are adjustable by extracting parameter values, units, descriptions, ranges, and derived dependencies from source code.

Instructions

Parse parameter variables from OpenSCAD code.

        Extracts named dimension variables from the top of an OpenSCAD
        file, including their values, units, descriptions, and valid
        ranges (if annotated in comments).

        Use this after generating OpenSCAD code to discover which
        parameters can be adjusted. A parameter computed from others
        (``inner = outer - 2*wall;``) is returned with ``derived: true``,
        its ``expression`` and ``depends_on``; it moves when those
        change and cannot be set directly.

        Args:
            scad_code: OpenSCAD source code string.

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>"
    },
    "name": "parse_scad_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
scad_codeYesOpenSCAD source code string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • 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?

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral detail about derived parameters, including that they carry derived/expression/depends_on fields and cannot be set directly, though it does not cover parse-failure behavior.

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 description is front-loaded with purpose and extraction behavior, and the derived-parameter note is valuable. It is slightly padded by the Args section, which repeats the sole parameter already covered by the schema.

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 one-parameter read-only parser with no output schema, the description adequately explains what will be returned: values, units, descriptions, ranges, and derived-parameter metadata. It leaves some edge cases unstated, such as malformed input handling, but is otherwise complete enough to call correctly.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents scad_code fully. The description's Args section simply repeats that same meaning without adding syntax, constraints, or examples.

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 states a specific verb and resource: parsing parameter variables from OpenSCAD code. It explains what is extracted and why, but it does not explicitly differentiate itself from nearby siblings such as validate_scad_parameters or analyze_scad_code.

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?

It gives a clear usage context: use after generating OpenSCAD code to discover adjustable parameters. It does not name alternatives or state when not to use this tool, so it falls short of full when/when-not guidance.

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