Skip to main content
Glama

Typebar (formerly SuperDocs)

open_documents

Load one or more SAVED documents into a session as editable tabs. The SAME durable document is attached (never copied), so edits flow back to the one shared row with cross-session soft-collaboration. The first listed document is focused. Returns the refreshed document roster so the client can render tabs immediately.

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>",
      "document_ids": "<document_ids>"
    },
    "name": "open_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
document_idsYesDurable document ids (from GET /v1/documents) to open into the 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

B3.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, and it does disclose real behavior: shared-not-copied semantics, edit propagation, soft collaboration, first-listed focus, and the returned roster. It omits what an agent most needs for a mutation: behavior when a document is already open, permission/auth requirements, limits on batch size, and failure modes. Good but materially incomplete for an unannotated mutating tool.

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?

Four tight sentences, front-loaded with the action and resource, then the shared-document guarantee, then ordering, then the return value. Nothing is redundant and each sentence carries distinct information.

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 no annotations and no output schema, the description does the heavy lifting: it explains the shared-row mutation model and states what is returned (refreshed roster), which covers the return-value gap. Still missing is preconditions/error behavior when re-opening a document or passing invalid ids.

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 67%, with include_html extensively documented (token-light default, web-app rationale) and document_ids described, leaving session_id bare. The description adds one genuinely new semantic — list order determines which tab is focused — but says nothing about session_id or how many ids can be passed in one call.

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?

Specific verb ("Load") plus resource ("SAVED documents into a session as editable tabs") with a stated side effect (attached, not copied). It separates itself from list_documents/get_document_detail by implying session attachment, though it never names a sibling (e.g., focus_session_document, list_session_documents) to draw the boundary explicitly.

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?

The word "SAVED" and the schema hint "durable document ids (from GET /v1/documents)" imply a prerequisite, and "editable tabs" implies intent. But there is no explicit when-to-use/when-not, and no guidance on choosing this over focus_session_document, list_session_documents, or get_document_detail — the agent must infer.

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.