Mithwire MCP

session_trace_export

Export a recorded browser session trace to a JSON file by specifying the session ID and output path, enabling offline analysis and debugging of navigation, console, and network activity.

Instructions

Export recorded trace to a JSON file.

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>",
      "output_path": "<output_path>"
    },
    "name": "session_trace_export"
  }
}

Input Schema

Name	Required	Description	Default
`session_id`	Yes
`output_path`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Oct 18, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet only says it exports to a file. It omits whether the trace must be stopped, whether output_path is overwritten, path constraints, and permission/auth requirements for a tool that clearly writes to disk.

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?

A single tight sentence with the action front-loaded and no filler. It is efficient, though its brevity reflects under-specification rather than disciplined conciseness.

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?

An output schema exists, so return values need not be described, but for a two-parameter write-to-disk tool with no annotations and 0% schema coverage the description is too thin. It leaves preconditions and side effects unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, so the description must compensate and largely does not. It only implies output_path (a JSON file) and session_id (the recorded trace), with no format, path syntax, or validity details.

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 (export), resource (recorded trace), and output format (JSON file), so the action is unambiguous. However, it does not distinguish itself from close siblings like session_trace_get or session_trace_replay, leaving the agent to infer which trace-access tool applies.

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?

There is no guidance on when to use this tool versus session_trace_get, session_trace_replay, or whether a trace must be started/stopped first. The agent receives no context or exclusions.

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

Deploy Server