Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Page speed

webops_pagespeed
Read-onlyIdempotent

A connected website's latest lab speed per measured page and the origin's real-user speed. Another organization's or an unconnected site answers not found. Read-only.

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": {
      "domain": "<domain>"
    },
    "name": "webops_pagespeed"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the trailing "Read-only" is largely redundant. The genuinely additive content is the not-found behavior for unconnected or foreign-organization domains, which is real behavioral context not present in the annotations. It still says nothing about latency, caching, or freshness of the "latest" measurement.

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 short sentences with the scope stated first and the error condition second; almost no waste. The phrasing "answers not found" is slightly telegraphic but understandable, and "Read-only" is a minor redundancy against the annotations.

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 single-parameter read tool with no output schema, the description covers what data is returned (per-page lab speed and origin real-user speed) and the main failure mode. The remaining gap is metric definition and units for "lab speed," which the agent cannot infer from a schema that has no output shape.

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?

Only one parameter exists and schema description coverage is 0%, so the description must carry the load. It implies `domain` identifies a connected website (unconnected domains yield not found), which adds real meaning, but it does not state the accepted domain format, whether scheme/www is allowed, or how it maps to the website list.

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 resource pair: per-page lab speed plus origin-level real-user speed, which is a meaningful distinction an agent can act on. It stops short of naming a sibling or stating an explicit retrieval verb, so differentiation from tools like webops_pages or webops_measurement is left to inference.

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?

It gives a useful negative condition: another organization's site or an unconnected site returns not found, which tells the agent the prerequisite is a connected website. However, it never states when to prefer this over related siblings (e.g. pages, measurement) or what to do instead when the site is unconnected.

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