Skip to main content
Glama

desktop_trace_export

Exports a self-contained HTML trace viewer from desktop session events so you can inspect and share recorded activity.

Instructions

agent-desktop trace export: Export a self-contained HTML trace viewer

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

Input Schema

NameRequiredDescriptionDefault
outNoOutput HTML path (default trace-<session>.html)
limitNoEmbed the last N merged events (0 for all; default 5000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/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. It discloses that the output is a self-contained HTML trace viewer, but it does not state whether an existing file is overwritten, whether directories are created, what permissions are needed, or what happens if no trace exists.

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 definition is a single compact sentence with the core purpose front-loaded. The 'agent-desktop trace export:' prefix is slightly redundant with the tool name, but there is no wasted prose.

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?

For a simple two-parameter export tool with fully documented schema fields, the description adequately states the output form. However, it omits the relationship to desktop_trace_show and file-writing behavior, which leaves meaningful gaps for an agent deciding whether and how to invoke it.

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 description coverage is 100%, so both the output path and event limit are already documented in the schema. The description adds only high-level context that the exported artifact is a self-contained HTML viewer, which is enough for the baseline but not beyond it.

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?

The description states a specific verb and resource: Export, producing a self-contained HTML trace viewer. It is clear what the tool does, though it does not explicitly distinguish itself from the sibling desktop_trace_show.

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 explicit guidance on when to use this export tool versus desktop_trace_show or when not to use it. The purpose implies exporting a trace, but the agent receives no conditions, prerequisites, or alternatives.

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