Skip to main content
Glama

browser_performance

Read-onlyIdempotent

Retrieve read-only browser timing metrics and a summary of slow resources for the current approved page to diagnose load performance.

Instructions

Read-only browser timing and slow resource summary of the current approved page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile needs no restating, and 'Read-only' merely repeats it. The description does add real context beyond the annotations: the scope is the current page and that page must be 'approved'. It omits what happens when no approved page exists and gives no sense of cost or payload size.

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?

A single front-loaded sentence with the read-only nature, the metric domain, and the target scope all stated compactly. No filler, no restatement of the tool name as a separate sentence.

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

Completeness4/5

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

For a zero-parameter, annotation-covered tool with no output schema, the description covers what is measured and which page it applies to, which is close to sufficient. It could be sharper about the returned shape (timing metrics vs. slow-resource list) and the failure mode when no page is open, but nothing essential for correct invocation is missing.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies the target page is implicit rather than passed as an argument.

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 names a specific resource and output ('browser timing and slow resource summary') for a specific target ('the current approved page'), so the agent knows it retrieves performance metrics rather than a snapshot, screenshot, or audit. It stops short of distinguishing itself from close siblings like browser_diagnostics or browser_source_probe, which an agent could plausibly confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'the current approved page' signals a precondition (a page must already be opened and approved) but never says so explicitly or names which sibling to use instead for diagnostics, audits, or page state. There is no when-not-to-use guidance, so the agent must infer the workflow position.

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