Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

get_devices_status

List all devices in the Sauce Labs data center with their current states, including availability, usage, and private device information.

Instructions

    Returns a list of devices in the data center along with their current states. Each device is represented by a
    descriptor, indicating its model, and includes information on availability, usage status, and whether it is
    designated as a private device. Note that the inUseBy field is exposed only for private devices
    isPrivateDevice: true. Users can view information about who is currently using the device only if they have
    the required permissions. Lack of permissions will result in the inUseBy field being omitted from the response
    for private devices.

    This tool provides a lightweight overview of all devices. For detailed device specifications, use the
    get_specific_device tool with the descriptor value as the device_id parameter.

    Available States:
        AVAILABLE	Device is available and ready to be allocated
        IN_USE	    Device is currently in use
        CLEANING	Device is being cleaned (only available for private devices)
        MAINTENANCE	Device is in maintenance (only available for private devices)
        REBOOTING	Device is rebooting (only available for private devices)
        OFFLINE	    Device is offline (only available for private devices)

    Note: The 'descriptor' field in each device object is the device identifier that should be used as the
    'device_id' parameter in get_specific_device calls.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: the inUseBy field exposure condition (private devices + permissions), the available states list, and the use of descriptor as an identifier for other tools. This is comprehensive.

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 description is well-structured with paragraphs, a state list, and a note. It is informative but slightly lengthy; however, every sentence adds value. Could be slightly more concise but still good.

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

Completeness5/5

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

Given the tool has no parameters and an output schema exists, the description adequately covers the output fields, special behaviors, state meanings, and cross-reference to a related tool. It is complete for its simplicity.

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?

There are 0 parameters, and the schema coverage is 100% (empty schema). According to guidelines, the baseline is 4. The description adds no parameter info because none exist, which is appropriate.

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 it returns a list of devices with their states, and differentiates itself from get_specific_device by noting that the latter provides detailed specifications. It also implies a lightweight overview purpose.

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 explicitly tells when to use get_specific_device for detailed specs, but does not mention alternatives like get_private_devices, which is a sibling tool specifically for private devices. The context is clear but lacks exclusions for all related siblings.

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/saucelabs/sauce-api-mcp'

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