Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

untrust_printer

Destructive

Remove a printer's hostname or IP from the trusted whitelist to revoke its access to your 3D printing environment.

Instructions

Remove a printer hostname/IP from the trusted whitelist.

        Args:
            host: The hostname or IP address to untrust.

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": {
      "host": "<host>"
    },
    "name": "untrust_printer"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe hostname or IP address to untrust.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / host / description
      Added value: +"The hostname or IP address to untrust."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is conveyed structurally. The description adds only the concept of a 'trusted whitelist' and says nothing about consequences (e.g., whether the printer becomes unreachable for printing, whether an active lock or job is affected, or whether the removal is reversible).

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 purpose sentence is front-loaded and the tool is small enough that the duplicated Args block costs little. The one-line restatement of the schema field is redundant but not obscuring.

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 simple one-parameter mutation with annotations covering destructiveness and no output schema, the description is minimally adequate. However, an agent would benefit from knowing that untrusting may break subsequent printing to that host and whether the host must currently be trusted — neither is stated.

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?

There is one parameter with 100% schema description coverage, and the description's Args block repeats the schema text verbatim ('The hostname or IP address to untrust'). It adds no format guidance, no matching semantics (exact string vs. normalized hostname), and no error behavior for unknown hosts, so 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?

The description names a specific verb ('Remove') and resource ('printer hostname/IP from the trusted whitelist'), making the effect unambiguous. It does not explicitly name the complementary tools trust_printer or list_trusted_printers, so sibling differentiation is only implied by the whitelist wording.

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 implied by the whitelist framing — you call this to remove a host you previously trusted — but there is no explicit statement of when to prefer this over trust_printer or how to verify current trust state with list_trusted_printers. No preconditions or prerequisites are given.

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