Skip to main content
Glama
codeofaxel

Kiln

by codeofaxel
OverviewSchemaRelated ServersScoreDiscussions
Python

rotate_encryption_key

Re-encrypt all encrypted G-code files with a new passphrase. Preview changes with a dry run before executing the rotation.

Instructions

Rotate the G-code encryption key by re-encrypting all files.

        Scans *directory* recursively for encrypted G-code files, decrypts
        with the old passphrase, and re-encrypts with the new one.

        **Run with ``dry_run=True`` first** to preview which files would be
        affected.  Then call again with ``dry_run=False`` to execute.

        After rotation, update the ``KILN_ENCRYPTION_KEY`` environment
        variable to the new passphrase and restart the server.

        Args:
            old_passphrase: The current KILN_ENCRYPTION_KEY value.
            new_passphrase: The new passphrase to encrypt with.
            directory: Root directory to scan for encrypted G-code files.
            pattern: Glob pattern for files to process (default ``"*.gcode"``).
            dry_run: Preview only — don't modify files (default ``True``).

        Requires Enterprise license and admin scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dry_runNo
patternNo*.gcode
directoryYes
new_passphraseYes
old_passphraseYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

No annotations provided, so description fully covers behavior: scans recursively, decrypts with old passphrase, re-encrypts with new, dry-run preview, and required post-rotation actions. Clearly states it modifies files. No contradictions.

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?

Well-structured: initial summary, then block with process, then parameter list. Front-loaded with main action. Slightly verbose with repetition (e.g., 'Scans *directory* recursively' and then parameter explanation), but overall clear and efficient.

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

Completeness5/5

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

Comprehensive for a 5-param tool with no output schema: covers purpose, process, prerequisites, post-conditions (env variable, restart), and parameter details. No gaps given the complexity and absence of annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description fully documents all 5 parameters. Explains each parameter's role (old_passphrase, new_passphrase, directory, pattern, dry_run), provides defaults, and clarifies dry_run usage. Adds meaning beyond schema field names.

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?

Description clearly states the tool's purpose: 'Rotate the G-code encryption key by re-encrypting all files.' It explains the process (scan, decrypt, re-encrypt) and distinguishes from siblings like encryption_status by focusing on the rotation operation.

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

Usage Guidelines5/5

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

Explicitly instructs to run with 'dry_run=True' first to preview, then with 'dry_run=False' to execute. Also provides post-rotation guidance: update environment variable and restart server. Mentions requirements: Enterprise license and admin scope. No alternative tools for rotation, so no need for exclusion.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/codeofaxel/kiln'

If you have feedback or need assistance with the MCP directory API, please join our Discord server