Skip to main content
Glama

Typebar (formerly SuperDocs)

init_session

Create a session AND open N saved documents into it in ONE call (the documents are SHARED, never copied — the same cross-session behavior as /documents/open). The web UI passes its own session_id so its session model stays consistent; an MCP/API integrator can omit it and the server mints one — the one-call way to start a session with documents already open. With no document_ids it just returns a fresh, empty session. The open semantics (first document focused, durable binding, returned roster) are identical to /documents/open.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "init_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idNoOptional client-chosen session id (the web UI passes its own so its session model stays consistent). Omit and the server mints one — the one-call way for an MCP/API integrator to start a session with documents already open.
document_idsNoDurable document ids (from GET /v1/documents) to open into the brand-new session. Omit/empty to start an empty session.
include_htmlNoInclude each document's full reassembled HTML body. Default false (token-light — recommended for AI agents enumerating or switching tabs): returns only ids, title, section count, focused flag, and page setup, omitting the body which can be hundreds of KB per document. The web app passes true to render document content.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does substantial work: documents are shared not copied, binding is durable, the first document is focused, and a roster is returned. It omits failure behavior (e.g., a session_id collision) and any permission or side-effect notes, which are meaningful for a creating tool.

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 compound behavior is front-loaded and the parenthetical about shared documents appears early. There is mild redundancy — 'one-call way' and the shared/never-copied point are repeated near-verbatim in the schema descriptions — but no filler sentences.

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?

Three optional parameters, no output schema, no annotations — the description covers the creation, the optional seeding, and the token-light return shape (ids, title, section count, focused flag, page setup). The main gap is error behavior on a duplicate session_id and whether an existing session is affected.

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%, so the baseline is 3. The description mostly restates what the schema already says (web UI passes session_id, omit for server-minted, include_html token tradeoff), adding emphasis rather than new meaning.

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?

States a specific compound verb and resource: create a session and open N documents in one call, with the same semantics as /documents/open. It clearly distinguishes itself from open_documents and list_sessions by emphasizing the single-call session bootstrap.

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?

Explains the two caller profiles (web UI passes session_id, MCP/API integrator omits it) and the no-document_ids degenerate case (fresh empty session). It doesn't name the actual sibling tools an agent might otherwise choose (open_documents, list_sessions), routing only to HTTP paths, so the alternative-selection guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.