umbra

Overview Schema Source Related Servers Discussions Admin

Session Load

session_load

Decrypts and injects saved cookies and localStorage into a browser tab before navigating auth-protected pages, enabling login-free access without re-authenticating.

Instructions

Decrypt + inject saved cookies/localStorage. Skips login. Load BEFORE auth-walled nav.

Ex: session_load('t0', 'github-me', 'hunter2') → {"name":"github-me","cookies":12,"localStorage_keys":4,"origin":"https://github.com"}

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": {
      "tab_id": "<tab_id>",
      "name": "<name>",
      "passphrase": "<passphrase>"
    },
    "name": "session_load"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`tab_id`	Yes
`passphrase`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 28, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations exist, so the description carries the full burden: it does disclose decryption with a passphrase, injection of cookies and localStorage, and that it bypasses login. It omits failure behavior (wrong passphrase), whether existing session state is overwritten, and any rate/permission constraints.

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?

One instruction sentence plus a compact call example; the ordering constraint is front-loaded and nothing is wasted.

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

Completeness3/5

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

An output schema exists, so return-value explanation is not strictly needed (the example's result JSON is largely redundant). For a 3-required-param, annotation-free mutation of browser session state, missing error/overwrite behavior is a real gap.

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 0%, so the description must compensate. The example maps concrete values onto the three parameters (tab id, session name, passphrase) and clarifies that passphrase is a decryption secret, but it leaves the tab_id counterpart semantics and name-uniqueness rules unexplained.

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?

States a specific verb+resource pair (decrypt + inject saved cookies/localStorage) plus the salient outcome (skips login). It is distinguishable from session_save/session_list, though it never names a sibling such as warm_session to sharpen the boundary.

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?

"Load BEFORE auth-walled nav" gives a concrete ordering/context rule for when to call it. It stops short of naming alternatives (warm_session, get_cookies/set_cookies) or when-not-to-use cases.

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

Deploy Server