Skip to main content
Glama
Sign In
Kloakt

Kloakt

by KultMember6Banger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

kloakt_session_open

Open or reattach to a persistent, named browser session that preserves cookies and page state across calls. Use to begin multi-step web interactions.

Instructions

Open (or reattach to) a persistent, named browser session. Unlike the stateless tools, a session keeps its cookies AND its page/JS/DOM state alive across separate calls, so you can log in once and keep driving the same page over many turns. A background daemon is auto-started if needed. Use this to begin a multi-step interaction; follow with kloakt_session_act / kloakt_session_read, and kloakt_session_close when done.

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

Input Schema

NameRequiredDescriptionDefault
urlNoOptional URL to open the page at
nameYesSession name (your handle for it)
portNoDaemon port (default: 9222)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.2/5.0
Behavior4/5

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

Without annotations, the description carries the burden of disclosing behavior. It explains that the tool keeps cookies and JS/DOM state across calls and that a background daemon is auto-started. However, it could mention session timeout, resource usage, or error handling, so it is not exhaustive.

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?

The description is concise (two sentences), front-loaded with the purpose, and efficiently explains the tool's value and usage flow without unnecessary words.

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?

The description is complete for a tool with no output schema and full parameter schema coverage. It explains the tool's role in a multi-step workflow and how it relates to sibling tools. However, it does not describe the return value or output format, which could be clarified.

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%, so the description adds little beyond what is already in the schema. The description mentions 'name' as a handle and 'url' as optional, but does not provide additional semantics or usage tips for the parameters.

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's purpose: to open or reattach to a persistent, named browser session that retains state. It explicitly differentiates from stateless tools and mentions keeping cookies and DOM state, distinguishing it from siblings like kloakt_session_act and kloakt_session_read.

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

Usage Guidelines4/5

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

The description provides clear usage guidance: 'Use this to begin a multi-step interaction; follow with kloakt_session_act / kloakt_session_read, and kloakt_session_close when done.' It contrasts with stateless tools but lacks explicit 'do not use' scenarios, which is acceptable given the context.

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