Skip to main content
Glama

How sites on a platform do, from the WebSpeed base

platform_benchmark
Read-only

What typically slows sites on a website platform down (WordPress, WooCommerce, Squarespace, Wix, Duda, Tilda, Divi, Bitrix), measured across the WebSpeed audit base: the share of audited sites of that platform with each bottleneck, the number of audits and the snapshot date, plus published before/after teardowns and studies for the platform. Use when the user asks why their Squarespace / WordPress / … site is slow, what is normal for the platform, or what they can fix on it.

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": {
      "platform": "<platform>"
    },
    "name": "platform_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPlatform name, e.g. WordPress, Squarespace, Wix

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare it read-only, non-destructive, and closed-world. The description adds genuinely useful context beyond that: the data is a cross-site audit aggregate with a snapshot date and sample size, not a live measurement of the user's site. It does not say what happens when the platform has no or few audits.

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, the first front-loading what the tool returns and the second front-loading when to use it. The long parenthetical platform list is dense but earns its place by telling the agent which inputs are in scope.

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 must convey return contents, and it does: per-bottleneck share of audited sites, audit counts, snapshot date, plus before/after studies. Only edge behavior (unsupported platform, thin sample) is left unspecified.

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% with a single required platform string, so the schema carries the structural burden and baseline is 3. The description does extend the enum-like list of supported platforms to WooCommerce, Duda, Tilda, Divi, and Bitrix, which is a modest but real semantic addition beyond the schema's three examples.

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 and aggregation: bottleneck prevalence per platform across the WebSpeed audit base, with audit counts, snapshot date, and published teardowns. It is clearly distinct from site-specific siblings like measure_site or get_measurement, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives concrete trigger scenarios: when a user asks why their WordPress/Squarespace site is slow, what is normal for the platform, or what they can fix. It stops short of stating exclusions, e.g. that a single-site measurement should go to measure_site instead.

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