Skip to main content
Glama

MCP Server By TestMu AI

by com.lambdatest.mcp
OverviewDiscussionsAdmin

Get Supported Platforms

getSupportedPlatforms
Read-only

Lists the OS, browser and device combinations LambdaTest supports, to find valid os, browser and version values for a test configuration. With no filters it returns a compact summary: each desktop OS with its browsers (version count, newest and oldest) and resolutions, and each mobile platform with its device count and OS versions. Set os (and optionally browser) for the full version list, or os=ios / os=android for device names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNoOS name to expand, matched case-insensitively as a substring, e.g. "Windows 11", "Sonoma", "android"
typeNoOnly desktop OSes or only mobile platforms
browserNoBrowser to expand on desktop, e.g. "chrome", "firefox", "edge", "safari"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / browser
      Added value: +{
+  "description": "Browser to expand on desktop, e.g. \"chrome\", \"firefox\", \"edge\", \"safari\"",
+  "type": "string"
+}
    • addedInput schema / properties / os
      Added value: +{
+  "description": "OS name to expand, matched case-insensitively as a substring, e.g. \"Windows 11\", \"Sonoma\", \"android\"",
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Only desktop OSes or only mobile platforms",
+  "enum": [
+    "desktop",
+    "mobile"
+  ],
+  "type": "string"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real behavioral context the annotations don't: the exact shape of the unfiltered response (per-OS browser counts, newest/oldest versions, resolutions; per-mobile device counts and OS versions) and how filters change the output.

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?

Front-loads what the tool returns, then the filter modes, with no filler sentences. The second and third sentences are dense (nested counts, resolutions, version ranges), but every clause carries information an agent needs.

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 describing the return shape in each mode, and annotations cover the safety profile. Missing only minor operational details such as result size or any cap on the unfiltered summary.

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%, so per-parameter meaning is already documented and the baseline is 3. The description goes beyond it by explaining parameter interaction — that os+browser yields a full version list while os=ios/os=android yields device names — which the schema's individual field descriptions do not convey.

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?

States a specific verb and resource ('Lists the OS, browser and device combinations LambdaTest supports') plus the downstream purpose ('to find valid os, browser and version values for a test configuration'). This distinguishes it from nearby siblings like listDevicesForTesting and getMobileCapabilityGenerator, which serve different lookups.

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?

Clearly explains the three invocation modes: no filters for a compact summary, os (optionally browser) for full version lists, os=ios/os=android for device names. That is strong guidance on how to call it, but it never states when to prefer this tool over listDevicesForTesting or getMobileCapabilityGenerator.

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

All MCP Server By TestMu AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources