Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

export_safety_profile

Read-only

Export a printer model's full safety limits as a shareable JSON object for sharing with other users; uses community profiles first, then bundled profiles.

Instructions

Export a safety profile as a shareable JSON object.

Returns the full safety limits for a printer model in a format
suitable for sharing with other users.  Looks up community profiles
first, then falls back to bundled profiles.

Args:
    printer_model: Printer model identifier (e.g. ``"ender3"``,
        ``"bambu_x1c"``).

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

Input Schema

NameRequiredDescriptionDefault
printer_modelYesPrinter model identifier (e.g. ``"ender3"``, ``"bambu_x1c"``).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / printer_model / description
      Added value: +"Printer model identifier (e.g. ``\"ender3\"``, ``\"bambu_x1c\"``)."
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly/closed-world safety, and the description adds genuine behavioral context by disclosing the lookup precedence: community profiles are checked first, then bundled profiles are used as a fallback. It does not describe failure behavior for an unknown printer model, but the resolution order is real information beyond the structured fields.

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 first sentence front-loads the action and return format, followed by a useful note on profile resolution. The Args block is a verbatim duplicate of the schema's property description, which is minor waste but not damaging.

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 single-parameter, read-only export tool with annotations and no output schema, the description covers what is exported, the format, and where the data comes from. Only the behavior for an unrecognized printer model is left unstated.

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% for the single required parameter, so the baseline is 3. The Args section simply restates the schema's type and examples ('ender3', 'bambu_x1c') without adding lookup semantics such as whether the identifier is case-sensitive or which models have community coverage.

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 and resource ('Export a safety profile') plus the output form ('shareable JSON object'), which is clear enough to distinguish it from get_safety_profile. It never names a sibling explicitly, though, so the distinction from get_safety_profile/list_safety_profiles is left to inference.

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?

Usage is only implied by the phrase 'suitable for sharing with other users', which hints at when you would export rather than merely read. There is no explicit when-to-use rule, no exclusion of get_safety_profile or list_safety_profiles, and no note on error conditions.

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