Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

unlock_safety_profile

Destructive

Unlock a locked safety profile to allow community profile modifications for a printer model again. Use it when a profile's edits are restricted and need to be re-enabled.

Instructions

Unlock a previously locked safety profile.

        Enterprise feature. Allows community profile modifications for
        this printer model again.

        Args:
            printer_model: Profile identifier to unlock.

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": "unlock_safety_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
printer_modelYesProfile identifier to unlock.

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 unlock."
  2. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety profile is set. The description adds real context the annotations don't: it is an enterprise-gated action that re-enables community profile modifications for a printer model. It does not say what risk the unlock re-exposes or whether the change is audited/reversible, which matters for a destructive tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prose is short and front-loaded, but the docstring-style Args block duplicates the parameter description verbatim and adds no value. Could be trimmed to two sentences with nothing lost.

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

Completeness3/5

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

For a single-parameter tool with a clear destructive annotation and no output schema, the description covers what it does and who can call it. It leaves out prerequisites (how to discover a locked profile, tier check failure behavior, audit trail), which are the main open questions before invoking a destructive unlock.

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 coverage is 100% and the Args line merely repeats the schema's own text ('Profile identifier to unlock'), adding no format, lookup, or validation guidance. Baseline 3 applies.

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?

States a specific verb (unlock) and resource (safety profile), with the precondition that it was 'previously locked'. It implicitly contrasts with the sibling lock_safety_profile but never names it.

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

Usage Guidelines3/5

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

The 'previously locked' precondition implies when this applies, and 'Enterprise feature' flags a gating requirement. There is no explicit statement of when not to use it or a pointer to lock_safety_profile / list_safety_profiles for the read-side workflow.

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