Skip to main content
Glama

upgrade_kiln

Update the Kiln package to the latest version after user confirmation. Defers update if a print is active to avoid interruption.

Instructions

Update the Kiln package to the latest version — for the user.

        The Apple-grade upgrade path. When a newer Kiln is available (or a
        hosted call returns an upgrade-required signal), OFFER to handle it:
        ask "want me to update Kiln for you now?" and call this with
        confirm=True once they agree. Don't make the user run a pip command.

        AGENT CONTRACT (important):
          * NEVER call this while a print is active — wait until it finishes.
            Swapping Kiln mid-print is unsafe.
          * Confirm with the user first; this changes their installed
            software. Pass confirm=True only after they say yes.
          * On success the new version is on disk but the running Kiln still
            has the old code loaded — relay the restart instruction from the
            result so the user applies it at a safe moment (not mid-print).

        Args:
            confirm: Set True to actually perform the update. Called without
                it, this returns the offer to show the user and changes
                nothing.
            force: Override the mid-print safety defer — only when the user
                explicitly insists.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNo
confirmNo
Behavior5/5

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

No annotations provided, but the description fully discloses behavioral traits: it changes installed software, is safe to call without confirm (returns offer only), swapping mid-print is unsafe, force override exists, and after success the old code remains loaded requiring a restart.

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 well-structured with clear sections (purpose, agent contract, args), but contains somewhat verbose marketing language ('Apple-grade upgrade path') that adds little value. Still, every sentence earns its place overall.

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?

Despite no output schema, the description covers preconditions (no active print), user confirmation, side effects, and what to do with the result (relay restart instruction). No gaps remain for effective use.

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 has 0% description coverage, but the description adds full meaning: confirm=True performs update, confirm=False returns offer; force overrides mid-print safety defer. This compensates completely.

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?

The description clearly states the verb 'Update' and resource 'Kiln package to the latest version', and distinguishes from sibling tools like 'get_upgrade_url' or 'kiln_health' by specifying the user-facing upgrade process.

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?

The description provides explicit guidance on when to call (when newer Kiln available), user confirmation, avoiding mid-print calls, and how to handle success (restart instruction). It also instructs to offer the upgrade rather than making the user run a command.

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