Skip to main content
Glama

Explain a speed metric with WebSpeed base numbers

explain_metric
Read-only

What a page-speed metric or term means, its good / needs-improvement / poor thresholds, and how real sites score on it: the median and the share of sites within the "good" line across the WebSpeed audit base (mobile lab runs of thousands of original sites), with the sample size and snapshot date. Also how many sites apply a technique such as fetchpriority, lazy loading or font-display. Use when the user asks whether a value is good or bad ("is an LCP of 4 s bad?"), what LCP / CLS / TBT / INP / TTFB / Speed Index / PageSpeed score means, or how other sites compare. For why a score changes between runs, use find_research.

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": {
      "metric": "<metric>"
    },
    "name": "explain_metric"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricYesMetric or term, e.g. LCP, Largest Contentful Paint, CLS, TBT, INP, TTFB, Speed Index, PageSpeed score, fetchpriority, font-display

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, non-destructive, not open-world), so the description focuses on valuable behavioral context: the data comes from mobile lab runs of thousands of original sites, includes sample size and snapshot date, and reports medians and share of good sites. It does not detail response formatting or unknown-metric handling, but for a read-only informational tool the added provenance and freshness information is substantial.

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?

The description is front-loaded with the returned data and then moves to usage guidance, which is the right order. It is dense and contains some awkward fragments ('Also how many sites apply...'), but nearly every clause adds specific information about thresholds, data provenance, or usage triggers.

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?

This is a simple one-parameter read-only lookup tool with no output schema, and the description does the important work of explaining what the response contains: metric meaning, thresholds, median, good-site share, sample size, snapshot date, and technique adoption. The main omission is what happens when the metric term is unknown or ambiguous, but otherwise an agent has enough to invoke it correctly.

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 the parameter is already well documented with examples such as LCP, CLS, TTFB, Speed Index, fetchpriority and font-display. The description adds the framing that techniques like fetchpriority, lazy loading or font-display are valid inputs, but otherwise mostly restates the schema examples. Baseline 3 is appropriate.

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?

The description states the specific resource clearly: page-speed metric meaning, good/needs-improvement/poor thresholds, WebSpeed audit-base median and good-site share, sample size and snapshot date, plus technique adoption rates. It also distinguishes this lookup/explanatory purpose from find_research for score-change analysis. An agent can identify both what the tool returns and what it is not for.

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

Usage Guidelines5/5

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

It gives explicit usage triggers: asking whether a value is good or bad (with an LCP 4 s example), what a metric or term means, or how other sites compare. It also names find_research as the alternative for 'why a score changes between runs', providing both when-to-use and a clear exclusion for a different question type.

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