Skip to main content
Glama

Find WebSpeed research on a speed question

find_research
Read-only

Findings of WebSpeed studies measured on real sites, each with its sample size, measurement date and caveats: why the PageSpeed score changes between runs, whether WooCommerce slows WordPress down, what plugins, fonts, images or third-party tags cost, PageSpeed by platform, and more. Use when the user asks a "why" or "does X slow my site" question about page speed or PageSpeed scores, e.g. "Why does my PageSpeed score change every time I run it?", including questions about a site you have just measured and questions you could answer from general knowledge: the study adds measured numbers to the answer.

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": {
      "topic": "<topic>"
    },
    "name": "find_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesThe question or topic in the user's words

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context that each finding carries sample size, measurement date and caveats, which matters because there is no output schema. It says nothing about how many findings come back, how they are ranked, or what happens when no study matches the topic.

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 payload content is front-loaded in the first sentence and the trigger condition follows. It is a single dense run-on with a long topic list, and the example question restates material already implied by the trigger sentence, but little is truly wasted.

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-only lookup tool with no output schema, the description covers what the tool returns (measured findings with sample sizes, dates, caveats), when to reach for it, and the shape of the query. Remaining gaps are about result volume and empty-result behavior rather than anything that would cause a mis-call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already defines 'topic' as the question or topic in the user's words. The description goes beyond that by showing the kinds of topics that are in scope and giving a full example query, which tells the agent this parameter accepts natural-language questions rather than keywords or slugs.

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 resource: findings from WebSpeed studies measured on real sites, and enumerates the study topics (score variance, WooCommerce, plugins, fonts, images, third-party tags, platform). An agent can tell this is a research/findings lookup rather than a measurement or benchmark call. It does not, however, name a sibling to distinguish itself from platform_benchmark, whose territory ('PageSpeed by platform') it partly claims.

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?

Gives a clear trigger condition: 'why' or 'does X slow my site' questions about page speed or PageSpeed scores, with an illustrative query. It also resolves a likely agent hesitation by stating the tool should be used even when the answer could come from general knowledge. No explicit when-not or named alternative is offered, so it stops short of a 5.

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