Skip to main content
Glama
Sign In
browser-dvr-mcp

browser-dvr-mcp

by funkyfunc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

browser_save_session

Save the current browser session as a replayable archive with full event timeline and keyframes. Enables later scrubbing and analysis of failures.

Instructions

TIME MACHINE. Durably save the current session as a replayable archive — the full provenance-tagged event timeline plus periodic visual/storage/state keyframes — so you (or a later session) can re-open and scrub it. Sessions are also auto-saved on browser_close; use this to snapshot mid-session or name it.

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": "browser_save_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional human-friendly name for the session.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The description details what is saved (provenance-tagged timeline, keyframes) and that it is durable. No annotations exist, so the description carries full burden. It lacks information on potential side effects or performance impact.

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 description is two sentences, efficiently packed with key information. The 'TIME MACHINE' opener is attention-grabbing but slightly extraneous. Overall, concise and well-organized.

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?

Given the simple parameter set (one optional param) and no output schema, the description adequately covers purpose, usage, and saved content. It could mention return value or error conditions but is mostly complete.

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?

The only parameter 'name' has a description in the schema and is repeated in the tool description. With 100% schema coverage, the description adds no extra semantic value beyond what the schema provides.

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 saves the current session as a replayable archive, distinguishing it from siblings like browser_load_session and browser_replay. The phrase 'TIME MACHINE' emphasizes its role as a durable snapshot.

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 explains when to use this tool ('snapshot mid-session or name it') and contrasts with auto-save on browser_close. However, it does not explicitly mention when not to use it relative to sibling tools like browser_save_scenario.

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