Skip to main content
Glama
Sign In
Kloakt

Kloakt

by KultMember6Banger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

kloakt_session_close

Close a persistent browsing session to release resources, dropping all associated pages and cookies. Use this when finished with a session.

Instructions

Close a persistent session, dropping its pages and cookies. Call this when you are done with a session opened by kloakt_session_open to free resources.

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

Input Schema

NameRequiredDescriptionDefault
nameYesSession name to close

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.7/5.0
Behavior5/5

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

Discloses side effects: 'dropping its pages and cookies' and 'free resources.' No annotations provided, so description fully covers behavioral traits for a close operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no unnecessary words, front-loaded with main action and side effects.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 1-parameter tool with no output schema, the description completely covers purpose, usage, and side effects. No gaps remain.

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?

Only parameter 'name' is described in the schema with 'Session name to close.' Description adds no further meaning, so baseline score of 3 applies due to 100% schema coverage.

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 description clearly states the tool closes a session and drops its pages and cookies, differentiating it from sibling tools like kloakt_session_open (opens) and kloakt_session_list (lists).

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

Usage Guidelines5/5

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

Explicitly says 'Call this when you are done with a session opened by kloakt_session_open to free resources,' providing clear when-to-use guidance.

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