Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

lock_safety_profile

Destructive

Locks a printer model's safety profile to prevent agents from changing limits and reject community updates; only an admin can unlock it.

Instructions

Lock a safety profile so agents cannot modify its limits.

        Enterprise feature. When locked, community profile updates for this
        printer model are rejected. Only an admin can unlock.

        Args:
            printer_model: Profile identifier to lock (e.g. "ender3").

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": {
      "printer_model": "<printer_model>"
    },
    "name": "lock_safety_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
printer_modelYesProfile identifier to lock (e.g. "ender3").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / printer_model / description
      Added value: +"Profile identifier to lock (e.g. \"ender3\")."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description goes well beyond them by disclosing the actual consequence (community profile updates rejected), the gating (enterprise only), and the recovery path (only an admin can unlock). That is exactly the context an agent needs before performing a compounding, non-self-reversible mutation.

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?

Purpose is front-loaded in the first clause, and the follow-on sentences each carry distinct information (feature gating, effect, unlock authority). The trailing Args block is redundant with the schema but is short and clearly demarcated.

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?

For a single-parameter mutation with no output schema, the definition covers purpose, side effects, entitlement gating, and reversibility path. Nothing material needed to call it safely 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%, and the description's Args block repeats the schema text verbatim ("Profile identifier to lock (e.g. \"ender3\")"), adding no new meaning such as accepted identifier formats or model-name resolution. Baseline 3 applies when the schema already does the work.

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?

States a specific verb and resource ("Lock a safety profile") plus the concrete effect on behavior ("agents cannot modify its limits"). The lock verb implicitly and unambiguously pairs with the sibling unlock_safety_profile / add_safety_profile, so an agent can distinguish it without opening a schema.

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?

Gives clear preconditions for use: it is an enterprise feature and locking blocks community profile updates for that printer model. It does not explicitly name when to call unlock_safety_profile instead, but the lock/unlock framing makes the alternative obvious.

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