Skip to main content
Glama

Lepiej Widoczny – audyt WordPress/WooCommerce

Core Web Vitals z Google PageSpeed

pomiar_core_web_vitals
Read-onlyIdempotent

Mierzy szybkość strony przez Google PageSpeed Insights: wynik wydajności 0–100, LCP, CLS, TBT, FCP, waga strony oraz dane od prawdziwych użytkowników Chrome (CrUX), jeśli Google je ma. Trwa 15–40 s.

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": {
      "url": "<url>"
    },
    "name": "pomiar_core_web_vitals"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesAdres strony lub sklepu, np. twoj-sklep.pl
strategiaNoDomyślnie mobile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 open-world, so safety needs no explanation. The description adds genuinely new behavioral facts: the 15–40 s duration (which matters for agent timeouts) and that CrUX field data is returned only 'if Google has it', i.e. conditionally available. It does not mention quota/rate limits or failure modes for unreachable URLs, keeping it at a 4.

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?

Two sentences, both front-loaded with the most decision-relevant facts: first what is measured and returned, then how long it takes. The metric list is dense but each item earns its place by telling the agent what it will receive. Nothing is repeated from the name or schema.

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?

There is no output schema, so the description must describe the return payload — and it does, enumerating the metric set and noting CrUX data is conditional. Latency is disclosed. The gaps are minor: no mention of error behavior for invalid/unreachable URLs and no note on API quota exhaustion, which an agent calling an external Google service would benefit from knowing.

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 both 'url' and the 'strategia' enum are already documented, including the mobile default. The description adds no extra meaning about parameter format, acceptable URL forms, or how strategy affects the returned metrics. Baseline 3 applies when the schema carries the parameter burden.

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 a specific verb and resource ('Mierzy szybkość strony przez Google PageSpeed Insights') and enumerates exactly which metrics come back (wynik 0–100, LCP, CLS, TBT, FCP, waga strony, CrUX). That is far more specific than a generic 'check performance' claim. It does not name or contrast itself with a sibling such as 'audyt_strony', 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 Guidelines3/5

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

Usage is only implied: the agent can infer this is the tool for a quick PageSpeed/Lighthouse-style measurement. There is no explicit statement of when to prefer it over 'audyt_strony', 'plan_poprawy' or 'porownaj_z_poprzednim', and no prerequisites or exclusions. The 15–40 s runtime hints at a one-off check but is not framed as guidance.

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