Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

performance_start_trace

Starts a browser performance trace to capture CPU profiling and rendering data, helping diagnose page performance issues.

Instructions

Start a performance trace (CPU profiling, rendering, etc.)

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

Input Schema

NameRequiredDescriptionDefault
categoriesNoComma-separated trace categories (default: all standard categories)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.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 behavioral burden, yet it says nothing about tracing overhead, whether the trace persists until explicitly stopped, or whether it can be started twice. For a stateful session-starting operation this is a meaningful gap.

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 short sentence, front-loaded with the action and resource, with no filler. It is efficient, though its brevity is partly under-specification rather than disciplined editing.

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?

For a tool that pairs with a stop operation and produces no output schema, the definition omits the essential lifecycle fact that results come from the companion stop call. An agent could call this and be unsure how to retrieve or terminate the trace.

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 coverage is 100% and the single optional `categories` parameter is fully documented in the schema with its default. The description adds only a light gloss on what categories cover (CPU, rendering), which does not go beyond the schema's own explanation.

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 and resource ("Start a performance trace") and the parenthetical "CPU profiling, rendering, etc." clarifies what the trace captures. It does not name or differentiate from the sibling performance_stop_trace, so an agent must infer the start/stop pairing from names alone.

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 versus alternatives, and critically no statement that performance_stop_trace must be called afterward to end collection and obtain results. Usage is only implied by the word "Start".

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