Skip to main content
Glama

webtool_performance_test

Identify device- and network-specific performance issues by running tests across multiple devices and network conditions and comparing results.

Instructions

Run performance tests across different devices and network conditions. Compare results and identify device-specific or network-specific issues.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the webpage to test
timeoutMsNoTimeout in milliseconds for each test
waitAfterLoadMsNoAdditional time to wait after page load for each test
useProxyNoWhether to use a proxy for this request
ignoreSSLErrorsNoWhether to ignore SSL certificate errors (use with caution)
devicesNoDevices to test on
networkConditionsNoNetwork conditions to test with
testsNoTests to run
compareResultsNoWhether to compare results between different scenarios
baselineDeviceNoDevice to use as baseline for comparisondesktop
baselineNetworkNoNetwork condition to use as baseline for comparisonWiFi
includeScreenshotsNoWhether to include screenshots in the results
runMultipleTimesNoWhether to run each test multiple times to get more accurate results
numberOfRunsNoNumber of runs to perform for each test if runMultipleTimes is true
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states what the tool does, not side effects, resource consumption, or whether it modifies state. It lacks details on rate limits, auth needs, or destructiveness.

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?

The description is two sentences, front-loaded with the core purpose. Every sentence adds value, with no extraneous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 14 parameters, no output schema, and no annotations, the description is insufficient. It doesn't explain the comparison logic, return format, or how multiple runs work. A more detailed description is needed for such a complex tool.

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%, so baseline is 3. The description adds no additional meaning beyond the schema; it mentions 'devices' and 'network conditions' generically, but doesn't elaborate on allowed values or usage nuances.

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 the tool's purpose: running performance tests across multiple devices and network conditions and comparing results. It distinguishes itself from siblings like webtool_lighthouse (Lighthouse audit) and webtool_web_vitals (vitals only) by focusing on cross-device/network comparison.

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 testing across devices/networks, but does not explicitly state when to use this tool over alternatives (e.g., webtool_lighthouse or webtool_web_vitals). No guidance on exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/misterboe/webtools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server