Skip to main content
Glama

desktop_trace_show

Merge session trace segments into a bounded JSON timeline, then filter by event-name prefix or cap the last N events to inspect recent desktop activity.

Instructions

agent-desktop trace show: Merge session trace segments into a bounded JSON timeline

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_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventNoFilter events by name prefix before applying --limit
limitNoReturn the last N merged events (0 for all; default 500)

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?

No annotations are supplied, so the description carries the full disclosure burden, yet it only says segments are merged into a bounded JSON timeline. It never states that this is a non-mutating read, whether it consumes or clears segments, or what happens when no trace segments exist.

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 front-loaded sentence with no padding; the operation and its output shape come first. It is arguably too terse rather than wasteful, which costs it only on other dimensions.

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 two-parameter, zero-required read tool with full schema coverage and no output schema, the description covers the core operation adequately. It leaves undefined what a trace segment is and whether the merge is destructive, which matters because there is no annotation coverage to fall back on.

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% and both parameters (event prefix filter, limit) are fully documented in the schema, so the baseline of 3 applies. The description's phrase "bounded" gestures at the limit but adds no filtering syntax or ordering detail beyond what the schema already states.

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 uses a concrete verb ("Merge") with a specific resource ("session trace segments") and a named output form ("bounded JSON timeline"), so the operation is unambiguous. It implies separation from the sibling desktop_trace_export by framing this as a merge/read view rather than an export, though it never states that contrast explicitly.

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 when-to-use guidance, no preconditions (e.g. whether a trace session must already be recording), and no mention of the sibling alternative desktop_trace_export. The agent must infer the retrieval scenario entirely from the verb.

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