Mcp-DOM

by IrMaho

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

import_session

Restore a recorded DOM session from raw JSON to enable time-travel debugging of UI mutations.

Instructions

Import a recording session bundle from raw JSON string.

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": {
      "bundleJson": "<bundleJson>"
    },
    "name": "import_session"
  }
}

Input Schema

Name	Required	Description	Default
`bundleJson`	Yes	Raw JSON string of the session bundle

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 1, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states that a bundle is imported, but does not say whether this creates a new session, overwrites an existing one, validates the JSON, or has other side effects. For a potentially destructive import operation, this is a significant gap.

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?

The description is one clear, front-loaded sentence with no filler. It communicates the core operation and input format efficiently.

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

Completeness2/5

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

There is no output schema and no annotations, and the tool description is minimal. Important context is missing, such as whether the import replaces or appends, what happens on invalid input, what the return value is, and any prerequisites. An agent cannot reliably determine the full behavior from this definition alone.

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 schema description for bundleJson ('Raw JSON string of the session bundle') fully covers the single parameter, and the tool description adds little beyond that. With 100% schema coverage, a baseline of 3 is appropriate.

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 states a specific verb ('Import') and resource ('recording session bundle') and clarifies the input format ('from raw JSON string'). This clearly distinguishes it from sibling tools like export_session and list_sessions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives, such as export_session or list_sessions. There is no mention of typical use cases, prerequisites, or situations where this tool should or should not be used.

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