Skip to main content
Glama

stop_trace

Stop an active browser trace and save it as a JSON file. Returns the absolute file path for use in Chrome DevTools.

Instructions

Stop the active trace and write it to disk as JSON.

    Returns the absolute file path. If ``file_path`` is empty, writes to
    a timestamped file in the system temp directory. The output matches
    the format that Chrome DevTools' "Load profile" accepts.

    Handlers and state are cleared via ``finally`` so a failed
    ``tracing.end()`` or a late ``tracingComplete`` never leaves the
    tool stuck on "a trace is already in progress" for the rest of the
    process.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description fully discloses behavioral traits: it writes to disk, returns file path, defaults to temp directory on empty file_path, matches Chrome DevTools format, and ensures cleanup via finally block to avoid stuck state. No annotations provided, so the description carries the full burden.

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 concise and well-structured: first sentence states the core action, followed by details on output, defaults, format, and cleanup. Every sentence adds value without redundancy.

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

Completeness5/5

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

Given the tool's complexity (stopping tracing, writing to disk, cleanup), the description covers all necessary aspects: return value, file behavior, format compatibility, and error handling. An output schema exists, so return values are further documented.

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

Parameters5/5

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

The schema has 0% parameter description coverage, but the description explains the 'file_path' parameter's effect: if empty, a timestamped file in temp directory is created. This adds essential meaning beyond the schema.

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 stops an active trace and writes it to disk as JSON, with specific details about the output file path and format. It distinguishes itself from sibling tools like 'start_trace' by focusing on stopping.

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 implicitly indicates usage when a trace is active, but does not explicitly state when not to use it or compare to alternatives. However, the context with sibling tools makes it clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bituq/zendriver-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server