Skip to main content
Glama
saucelabs

Sauce Labs MCP Server

Official
by saucelabs

get_devices_status

Check device availability and status in Sauce Labs testing platform to identify ready-to-use devices for test allocation.

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
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: the tool returns a list of devices with states, explains field visibility rules (inUseBy field only for private devices with permissions), and documents all possible device states with their meanings. It doesn't mention rate limits or auth requirements beyond permissions for inUseBy, but covers most operational aspects well.

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 clear sections: purpose, field behavior explanation, usage guidance, state definitions, and parameter mapping note. While comprehensive, it could be slightly more concise by integrating some details more tightly, but all sentences add value.

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 an output schema (which handles return structure), 0 parameters, and no annotations, the description provides excellent contextual completeness. It explains what the tool does, when to use it, behavioral nuances (field visibility, state meanings), and how outputs relate to other tools, covering all necessary aspects for agent understanding.

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?

The input schema has 0 parameters with 100% coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, maintaining focus on the tool's functionality and output characteristics.

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: 'Returns a list of devices in the data center along with their current states.' It specifies the verb ('Returns'), resource ('devices'), and scope ('in the data center'), and distinguishes it from sibling tools by contrasting with 'get_specific_device' for detailed specifications.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool vs. alternatives: 'This tool provides a lightweight overview of all devices. For detailed device specifications, use the get_specific_device tool...' It clearly defines the tool's role in the context of sibling tools.

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