Skip to main content
Glama

Seahawk Media

Test page speed

test_page_speed
Read-onlyIdempotent

Measure a public page with Google PageSpeed Insights: performance score, lab Core Web Vitals (LCP, CLS, TBT, FCP, speed index, TTFB), real-user field data where Google has it, and the biggest opportunities. Takes up to a minute. Same as https://seahawkmedia.com/tools/website-speed-test/.

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

Input Schema

NameRequiredDescriptionDefault
urlYesA public page address.
strategyNomobile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered; the description adds genuinely new behavioral context: a ~1 minute latency and the public-page requirement (implying auth-gated pages will fail). It omits any mention of rate limits or failure modes, 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?

Two sentences, front-loaded with the verb and resource, and the metric list earns its place by standing in for the absent output schema. Slightly list-heavy with no wasteful framing sentences.

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 usefully enumerates return contents (score, lab vitals, field data, opportunities) and warns about duration, which is enough to call the tool confidently. Missing pieces are the strategy parameter meaning and error behavior for non-public pages.

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 coverage is 50%: only 'url' is described, while 'strategy' has an enum and default but no explanation. The description reinforces that the url must be public but never mentions the mobile/desktop strategy parameter, so it only partially compensates for the coverage gap.

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?

States a specific verb and resource ('Measure a public page with Google PageSpeed Insights') and enumerates the returned metrics, so an agent knows exactly what comes back. It does not differentiate from the sibling check_website, which is the most likely source of ambiguity.

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 implied by 'Measure a public page' and the 'Takes up to a minute' note sets expectations, but there is no explicit when-to-use guidance or comparison to alternatives such as check_website. The requirement for a public URL is the only implicit precondition.

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