Skip to main content
Glama

browserless_performance_result

Read-onlyIdempotent

Retrieve an existing inline Lighthouse audit by its exact auditRef for follow-up analysis. Never starts or repeats an audit; if results are still pending, let the widget finish instead of polling.

Instructions

Retrieve an existing inline Lighthouse audit for follow-up analysis using its exact auditRef. Never starts or repeats an audit. If still pending, let the widget finish; do not poll.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "auditRef": "<auditRef>"
    },
    "name": "browserless_performance_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
auditRefYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.47.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful behavior beyond that: it is a pure fetch that will not trigger or repeat work, and pending results must not be polled. It says nothing about the shape of the returned audit or what happens when the auditRef is unknown or expired.

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?

Three tight sentences, front-loaded with the action, then the exclusion, then the pending-state handling. No filler or restatement of the tool name.

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 single-parameter read tool with full annotation coverage and no output schema, the description covers what an agent most needs to avoid misusing it: it does not re-run audits and pending states must not be polled. Missing only the non-essential detail of what the returned audit contains or how failures are surfaced.

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?

There is one required parameter with 0% schema description coverage, so the description must carry the load. It does clarify that the value is the audit's exact reference to an existing audit, implying the identifier must originate from a prior audit creation rather than being minted here. It does not explain format constraints (UUID) beyond what the schema's pattern already enforces, so the added meaning is modest.

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?

States a specific verb ('Retrieve'), a specific resource ('existing inline Lighthouse audit'), and the identifier it keys on ('exact auditRef'). The clause 'Never starts or repeats an audit' positively separates it from the audit-starting siblings without needing to name them.

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?

Gives clear usage context: only for already-existing audits, and explicit when-not behavior ('Never starts or repeats an audit'). It also prescribes what to do if the audit is still pending ('let the widget finish; do not poll'), which is actionable guidance. It does not name the sibling to use when you do need to start an audit, which keeps it short of a 5.

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