Skip to main content
Glama

Web vitals

get_web_vitals
Read-only

The web app's Core Web Vitals from real browsers: a 0 to 100 performance score (LCP 30%, INP 30%, CLS 15%, FCP 15%, TTFB 10%, Google's thresholds), each vital's p75 with its good / needs improvement / poor counts, and pages ranked by opportunity (how much the score would rise if that page scored 100).

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

Input Schema

NameRequiredDescriptionDefault
toNoAn ISO time, or how long ago (default now)
fromNoAn ISO time, or how long ago: 30m, 24h, 7d
rangeNoWindow: 1h, 24h, 7d, 14d, 30d or 90d (default 24h). Ignored when from is given.
sourceNobackend (servers), frontend (app and web), or all (default)
releaseNoOnly this release: 2.0.77+185, 2.0.77 (every build) or package@2.0.77+185
serviceNoOnly this service, like house-ai-api or the app's bundle id
environmentNoLike production. Default: production when the app has it, else its busiest non-development one. 'all' for every environment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / release / description
      Previous value: -"Only this release (service version)"New value: +"Only this release: 2.0.77+185, 2.0.77 (every build) or package@2.0.77+185"
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description goes beyond that by disclosing how the score is computed (LCP 30%, INP 30%, CLS 15%, FCP 15%, TTFB 10%), that aggregation is p75 with good/needs-improvement/poor buckets, and that pages are ranked by score uplift potential. It does not discuss data latency, sampling, or minimum-traffic caveats, which keeps it from a 5.

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?

It is a single front-loaded sentence that leads with the resource and then unpacks the return payload; every clause adds information. The nested parentheticals (weights, threshold labels, opportunity definition) make it dense to parse in one pass, but nothing is filler.

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 spends its budget explaining the return shape: score, per-vital p75 with rating counts, and ranked pages. Parameters are fully documented in the schema, so the remaining gap is only the absence of routing guidance versus sibling performance tools.

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% and all 7 parameters are optional with documented enums, defaults and formats, so the schema carries parameter meaning fully. The description adds no parameter-specific guidance, such as how release or environment interact with the score, or whether a narrow range degrades p75 reliability. Baseline 3 applies when the schema does the work.

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 states the specific resource and scope: "The web app's Core Web Vitals from real browsers," which implicitly separates it from the mobile-vitals sibling. It also enumerates the exact payload (score, per-vital p75 and thresholds, page opportunity ranking), so an agent knows what it gets. It never names a competing sibling explicitly, so it stops short of a 5.

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 mention of alternatives such as get_mobile_vitals or get_performance_overview. The agent must infer from the word "web" that this covers browser RUM rather than native apps. Nothing tells the agent what question this tool answers versus other performance tools.

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