Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_interception_history

Read-only

Retrieve recent interception results for a session, newest first, including actions taken, triggered rules, and reasons. Use it to review what was blocked or allowed and why.

Instructions

Get recent interception results for a session.

Args:
    session_id: Target session ID.
    limit: Maximum results to return (default 50, max 500).

Returns interception results from newest to oldest, including
actions taken, triggered rules, and reasons.

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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results to return (default 50, max 500). Default: 50.
session_idYesTarget session ID.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.5.1
    • changedInput schema / properties / limit / description
      Previous value: -"Default: 50."New value: +"Maximum results to return (default 50, max 500). Default: 50."
    • addedInput schema / properties / session_id / description
      Added value: +"Target session ID."
  2. Changed2 schema fields changedv1.5.0
    • removedInput schema / properties / limit / default
      Removed value: -50
    • addedInput schema / properties / limit / description
      Added value: +"Default: 50."
  3. 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 declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety and side-effect profile are covered. The description still adds genuine value beyond them by disclosing result ordering (newest to oldest) and the shape of each entry (actions taken, triggered rules, reasons), which tells an agent how to interpret and present the output.

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 description is short, front-loaded with the one-line purpose, and uses a conventional Args/Returns layout that is easy to scan. The Args block is largely redundant with the schema, so it is close to but not perfectly free of waste.

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?

With an output schema present, the description need not enumerate return fields, and annotations cover the safety profile; the remaining essentials (base session-scoped read, ordering, truncation cap) are present. The only missing piece is routing guidance toward the neighboring interception-session and status tools.

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 the Args section merely restates the schema text for session_id and limit, including the same default 50 / max 500 note. No additional semantics, such as how limit interacts with ordering when truncated, are added beyond the structured fields.

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: 'Get recent interception results for a session', with the scope (per-session, recent, ordered newest to oldest) made explicit. It is clear enough to separate from list_interception_sessions (sessions, not results) and get_interception_status, but it never names those siblings, so differentiation 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: you call it when you want the past interceptions of an existing session. There is no statement of when to prefer this over get_interception_status or list_interception_sessions, and no prerequisites such as requiring an active interception session or that session_id be valid.

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