Skip to main content
Glama
Sign In
@gridwork/siteaudit

@gridwork/siteaudit

by thegridwork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

audit_performance

Analyze page load time, size, render-blocking resources, DOM complexity, compression, caching, and image optimization to identify performance bottlenecks.

Instructions

Analyze a page's performance: load time, page size, render-blocking resources, DOM complexity, compression, caching, and image optimization.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to audit for performance

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations exist, so the description must bear full burden. It lists analysis areas but does not disclose safety (read-only), side effects, rate limits, or prerequisites, leaving the agent uncertain about operational context.

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?

The description is a single concise sentence listing key aspects, but it could be better structured (e.g., bullets) for readability. No wasted words.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the main purpose and metrics. However, it omits details about output format or response structure, which would improve completeness.

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% (the only parameter 'url' has a description). The tool description adds no extra meaning beyond the schema, so baseline score applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it analyzes page performance and lists specific metrics (load time, page size, etc.), distinguishing it from sibling tools like quick_check, audit_site, audit_accessibility, and audit_seo which cover other aspects.

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?

The description implies usage for performance analysis but provides no explicit guidance on when to use this tool versus siblings like quick_check or audit_site, nor any when-not conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools