Skip to main content
Glama
Sign In
Kloakt

Kloakt

by KultMember6Banger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

kloakt_session_read

Read a persistent session's page state without altering it. Choose text mode for the page's text or snapshot mode for an accessibility tree (optionally only interactive elements).

Instructions

Read the current state of a persistent session's page without changing it. mode='text' returns document.body.innerText; mode='snapshot' returns an indexed accessibility/structure tree (pass interactive=true for only the actionable elements). Use to observe what the page looks like now.

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

Input Schema

NameRequiredDescriptionDefault
modeNoWhat to read (default: text)text
nameYesSession name
interactiveNoFor mode=snapshot: only return actionable elements (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations provided, but description explicitly says 'without changing it', indicating read-only. Details return values for each mode and the interactive option, adding behavioral context beyond the schema.

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 concise sentences, front-loaded with core purpose. Every sentence adds information without redundancy.

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?

Tool has 3 simple params and no output schema; description explains return formats adequately. Could mention that the session must be open, but context from session tools implies it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema describes parameters with 100% coverage; description adds value by explaining what each mode returns (document.body.innerText vs accessibility tree) and how interactive filters for actionable elements.

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?

Description clearly states 'Read the current state of a persistent session's page without changing it', specifying the verb and resource. It distinguishes from siblings like kloakt_session_act and kloakt_screenshot by emphasizing read-only and non-modifying behavior.

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?

States 'Use to observe what the page looks like now', implying inspection context. No explicit exclusions or alternatives, but siblings cover other actions, providing implicit 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