Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_interception_status

Read-only

Retrieve status and statistics for a specified interception session, including session metadata, command counts, and current telemetry.

Instructions

Get status and statistics for an interception session.

Args:
    session_id: Target session ID.

Returns session metadata, command counts, and current telemetry.

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>"
    },
    "name": "get_interception_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesTarget session ID.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / session_id / description
      Added value: +"Target session ID."
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already define this as readOnlyHint: true and destructiveHint: false, establishing a safe behavioral baseline. The description supports this by stating it returns status and statistics, which confirms its read-only nature and provides context on the type of data returned, but adds no new behavioral restrictions.

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 definition is concise, efficiently covering the purpose, input, and general output in a brief, well-structured paragraph. It is direct and avoids superfluous phrasing.

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?

Since an output schema is implied (or available), the description does not need to detail every returned field. Instead, it successfully categorizes the return value (metadata, counts, telemetry), providing sufficient context for the agent to determine if the tool meets its operational needs.

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%, meaning the schema provides full definition of the 'session_id.' The description merely reiterates this, adding no semantic depth or constraints beyond the structured input fields provided by the schema.

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?

The tool clearly states its function as retrieving 'status and statistics' for a specific 'interception session.' Given the vast list of sibling tools (which includes many generic 'get' or 'list' actions), the specific reference to 'interception session' provides strong differentiation.

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 description is highly functional but lacks guidance on when to use it relative to alternatives. While the sibling list contains functions like 'add_interception_rule' and 'list_interception_sessions,' the description doesn't explicitly warn the agent against using those for status checks.

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