Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

Lab test

lab_test

Starts a lab test of an audit's page: Lighthouse run by Google PageSpeed Insights (performance, accessibility, best practices, SEO). Answers 202 at once; the test takes ~25 s to 2+ minutes — then read it with lab_result. Does not change the audit score. Answers 202 at once; the test runs for ~25 s to over 2 minutes and its summary is stored in the audit (summary.lab.<strategy>), so it comes back in GET /api/audits/:id, in the tab and in the shared report. It does not change the audit score. Calling again while the same strategy is running does not start a second test. Limits: 4 tests at a time on the server, 6 per network per hour and 500 per day for the whole product. Free: no x402 charge.

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": {
      "guest_token": "<guest_token>",
      "id": "<id>"
    },
    "name": "lab_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesaudit id
strategyNomobile (default) or desktop
guest_tokenYesPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / guest_token / description
      Added value: +"Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: async 202 semantics, run duration, deduplication of concurrent same-strategy calls, where output is persisted (summary.lab.<strategy>, visible in GET /api/audits/:id and the shared report), that the audit score is unaffected, concurrency and hourly/daily rate limits, and that it is free of x402 charge. This is exactly the operational context annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Content is front-loaded but literally duplicated: "Answers 202 at once" and "It does not change the audit score" each appear twice in near-identical wording, and the duration is restated. Several sentences do not earn their place, which dilutes an otherwise dense and useful payload.

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?

With no output schema, the description correctly explains that the response is just a 202 and that the actual summary lands in the audit document and is fetched via lab_result. Combined with limits and cost, an agent has enough to invoke and follow up correctly; only a hint about how to tell a run is still in progress is missing.

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%, so id, strategy and guest_token are already documented, including the mobile default. The description adds only indirect meaning via repeated references to "the same strategy" for dedupe behavior; it does not clarify token scope or strategy effects 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?

Names a specific verb and resource (starts a lab test of an audit's page), names the engine and the four measured categories, and distinguishes itself from the sibling that reads the result ("then read it with lab_result"). An agent can tell it apart from lab_result and audit_site without opening any schema.

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 context for use and an explicit follow-up path: the call returns 202 immediately and the result must be retrieved with lab_result after ~25 s to 2+ minutes. It also states what not to worry about (score unchanged, no second test if the same strategy is running). It stops short of saying when to choose this over a full audit_url run.

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

All pageaudit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources