Skip to main content
Glama

Page performance basics without a browser

page_weight
Read-only

Page performance basics without a browser: time to first byte, HTML size, compression, caching headers, CDN, and counts of scripts, stylesheets, images, fonts and iframes, with inline script/style size. Fast (1-3 s). Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.002 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, and the description adds genuine behavioral context on top: typical latency (1-3 s), a free quota of 20 calls/day per user, and paid overflow at $0.002/call via x402/USDC on Base. That quota-and-payment model is exactly the kind of operational detail annotations cannot express. It does not mention error behavior or result caching, which keeps it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the capability and metric inventory first, then speed followed by cost and quota. No redundancy, and the long metric clause is doing real discriminating work rather than padding.

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 compensates by listing the returned metrics, and it covers cost/quota for the non-obvious payment flow. For a read-only single-URL tool this is close to complete; only error/payment-failure behavior is left unstated.

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 100%, so both parameters (url, payment) are already documented in the schema, and the description adds no syntax or format detail beyond restating the x402/USDC-on-Base payment model. 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 enumerates exactly what the tool reports (TTFB, HTML size, compression, caching headers, CDN, counts of scripts/stylesheets/images/fonts/iframes, inline script/style size) and frames it as "page performance basics without a browser," which is specific enough to separate it from sibling tools like screenshots or seo_audit. It never uses an explicit verb such as "measures" or "analyzes a URL," but the resource and metric set make the purpose unambiguous.

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 the metric list and the "without a browser" framing (static, no-render perf snapshot for a single URL), so an agent can infer when it applies. However, no sibling is named as an alternative or exclusion, and there is no guidance on when a full headless-browser audit or a narrower tool like headers/images would be preferable.

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.