Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

remove_interception_rule

Destructive

Remove an interception rule from an active Kiln session using the session and rule IDs, stopping that rule from intercepting further activity without ending the session.

Instructions

Remove an interception rule from an active session.

Args:
    session_id: Target session ID.
    rule_id: The rule ID to remove.

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": {
      "session_id": "<session_id>",
      "rule_id": "<rule_id>"
    },
    "name": "remove_interception_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idYesThe rule ID to remove.
session_idYesTarget session ID.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • addedInput schema / properties / rule_id / description
      Added value: +"The rule ID to remove."
    • addedInput schema / properties / session_id / description
      Added value: +"Target session ID."
  2. First observedv0.1.0

TDQS

B3.2/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 the danger profile is covered structurally. The description adds one useful behavioral constraint — the rule must belong to an active session — but does not say whether removal is reversible, what happens if the rule ID is unknown, or whether the removal affects in-flight G-code interception.

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 operation is stated in the first sentence, and the parameter list is short and skimmable. The Args block largely restates schema text, which is minor redundancy rather than bloat.

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?

A two-parameter mutation tool with an output schema and full schema coverage is mostly self-describing, so the description does not need to cover return values. It is still thin on failure modes and on how the agent discovers a valid rule_id, which matters for a destructive operation.

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 both parameters are already documented identically in the schema, so the Args block adds no meaning beyond it. No format, validation, or lookup hints (e.g., how to obtain a rule_id) are provided, so the baseline of 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 states a specific verb and resource ('Remove an interception rule') and adds scope ('from an active session'), so the operation is unambiguous. It does not name or distinguish itself from siblings such as add_interception_rule or get_interception_status, leaving that inference to the agent.

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

Usage Guidelines2/5

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

No guidance on when to use this versus add_interception_rule, stop_gcode_interception, or load_safety_interception_rules, and no stated prerequisites such as requiring an already-active interception session. The 'active session' phrase hints at a precondition but never states what happens if the session is not active.

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