Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get lab test scores

audits_lab_results
Read-onlyIdempotent

Lighthouse scores (performance, accessibility, best practices, SEO) and Core Web Vitals for each page an audit tested, on mobile and desktop.

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": {
      "siteId": "<siteId>",
      "auditId": "<auditId>"
    },
    "name": "audits_lab_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYes
auditIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context beyond that. It does add useful scope detail: results are per-page and split across mobile and desktop, and the exact metric families returned are enumerated. It says nothing about result size, pagination, or what happens when an audit has no pages yet.

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 tight sentence with the metric list front-loaded and no filler. Slightly weakened by being a sentence fragment that never states an action, but nothing is wasted.

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 read-only retrieval tool with no output schema, the description adequately conveys what comes back: category scores plus Core Web Vitals, per page, per device. It is only missing prerequisite context (where auditId comes from) and any note on response size or ordering.

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

Parameters2/5

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

Schema description coverage is 0% for two required parameters, so the description must carry the burden. It only indirectly hints that auditId identifies 'an audit' and that results are scoped to the pages it 'tested'; siteId is never explained, nor is the maxLength=100 constraint or the expected ID format.

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 the concrete resource precisely: Lighthouse category scores (performance, accessibility, best practices, SEO) plus Core Web Vitals, broken out per tested page and per device. That is far more specific than the title 'Get lab test scores' and lets an agent distinguish it from analytics-style siblings and from seo_get_ai_visibility_results. It loses a point only because it is a noun phrase with no verb and no explicit contrast with a sibling.

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 when-to-use or when-not-to-use guidance, and no alternative is named. The agent must infer that an auditId from seo_list_site_audits is a prerequisite for calling this tool; the description never says so.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources