Skip to main content
Glama

MCP Server By TestMu AI

by com.lambdatest.mcp
OverviewDiscussionsAdmin

List Devices for Testing

listDevicesForTesting
Read-only

Lists the real devices available on LambdaTest for mobile app testing, 50 per page by default. Filter by region, OS, device name or OS version, and page with limit and offset. The text gives the total that matched.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNoOperating system filter
limitNoDevices per page, 1 to 200 (default 50)
offsetNoDevices to skip (default 0)
regionNoDevice region (default: us)
deviceNameNoDevice name to match, case-insensitively as a substring, e.g. "Galaxy S24", "iPhone 15", "Pixel"
platformVersionNoOS version to match, e.g. "14" (matches 14 and 14.x)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / deviceName
      Added value: +{
+  "description": "Device name to match, case-insensitively as a substring, e.g. \"Galaxy S24\", \"iPhone 15\", \"Pixel\"",
+  "type": "string"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Devices per page, 1 to 200 (default 50)",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Devices to skip (default 0)",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / platformVersion
      Added value: +{
+  "description": "OS version to match, e.g. \"14\" (matches 14 and 14.x)",
+  "type": "string"
+}
  2. First observed

TDQS

A3.8/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 the safety profile is covered. The description adds real value beyond that: the default page size of 50 and the fact that the response text reports the total number matched, which is the only source of return-shape information since there is no output schema.

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?

Three short sentences with zero filler: what it lists, the default page size, the filterable dimensions, and the returned total. The resource and default are front-loaded so the agent gets the essential facts immediately.

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 read-only paginated list tool with a fully documented schema and no output schema, the description covers pagination defaults, filter dimensions, and the returned total count. It is nearly complete, lacking only a note on ordering or how to interpret the matched-total value.

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% and every parameter is documented in the schema, including the substring/case-insensitive match semantics and the '14 matches 14.x' version behavior. The description only restates those same filters, so the baseline of 3 is appropriate with no added syntax or format detail.

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 verb and resource: 'Lists the real devices available on LambdaTest for mobile app testing', which clearly identifies a device-catalog read. It does not distinguish itself from the closest sibling (getSupportedPlatforms), which also concerns available platforms, so it stops short of a 5.

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?

Usage is implied rather than stated: the description explains that you can filter by region/OS/name/version and paginate, which hints at the discovery/search scenario. But it never says when to prefer this tool over getSupportedPlatforms or other listing siblings, and offers no exclusions or prerequisites.

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