Skip to main content
Glama

lava-mcp has moved

This repository has moved to https://github.com/lava-mcp/lava-mcp

Please update your remotes, bookmarks, and issue links:

git remote set-url origin git@github.com:lava-mcp/lava-mcp.git

All history, issues, and ongoing development live at the new location.

Available Tools

21 tools
cancel_jobB

Request cancellation of a running or queued job.

Inputs: job_id (required).

get_deviceB

Get the full record for one device by hostname.

Inputs: hostname (required).

get_device_dictionaryC

Get a device's rendered configuration dictionary (Jinja2/YAML text).

Inputs: hostname (required). Returns: result

get_jobA

Get the full record (state, health, device, times) for one job.

Inputs: job_id (required).

get_job_definitionA

Get the original submitted YAML job definition for a job.

Inputs: job_id (required). Returns: result

get_job_logsA

Get a job's logs (YAML). Optionally limit to the [start, end) line range.

Inputs: job_id (required), start, end. Returns: result

get_job_resultsC

Get a job's test-case results (pass/fail per case).

Inputs: job_id (required), limit.

get_lab_healthB

Get per-device health across the lab.

Inputs: no named parameters.

get_qdl_infoA

Summarise a device's QDL/flash capability (qdl/fastboot deploy + boot params).

Useful before flashing a Qualcomm board: reports whether the device supports qdl, the qdl deploy/boot method parameters, and all available deploy/boot methods, derived from the device's rendered configuration.

Inputs: hostname (required).

get_queueB

Get the queue of submitted jobs waiting for a device.

Inputs: no named parameters.

get_runningB

Get per-device-type running/reserved counts.

Inputs: no named parameters.

list_devicesA

List devices, optionally filtered by device_type, health or state.

Returns {count, results}. health is e.g. Good/Bad/Maintenance/Unknown; state is Idle/Reserved/Running.

Inputs: device_type, health, state, limit.

list_device_typesC

List the device types known to this LAVA instance.

Inputs: limit.

list_jobsB

List test jobs, newest first, with optional filters.

state is e.g. Submitted/Scheduling/Scheduled/Running/Canceling/Finished; health is Unknown/Complete/Incomplete/Canceled.

Inputs: state, health, submitter, device_type, +1 more.

list_workersA

List the dispatcher workers and their health/state.

Inputs: no named parameters.

resubmit_jobC

Resubmit a finished job with the same definition.

Inputs: job_id (required).

set_job_priorityB

Set a job's queue priority (0-100, higher runs sooner).

Inputs: job_id (required), priority (required).

submit_jobC

Submit a YAML job definition. Returns the new job id(s).

Inputs: definition (required).

validate_jobB

Validate a YAML job definition without submitting it.

Inputs: definition (required).

versionA

Return the version of the connected LAVA server.

Inputs: no named parameters.

whoamiA

Return the LAVA user your token authenticates as.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 21 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: device queries (get_device, get_device_dictionary, get_qdl_info) are clearly separated from job operations (submit, cancel, resubmit, set_priority, validate) and listings (list_devices, list_jobs, etc.). No two tools appear to overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_device, submit_job, list_devices). There are no deviations or mixed conventions.

    Tool Count3/5

    With 21 tools, the count falls in the 'borderline heavy' range (16-25). While each tool appears necessary, the set could potentially be trimmed by combining some closely related functions, but overall it remains functional.

    Completeness4/5

    The tool set covers core LAVA workflows: device inspection, job lifecycle (submit, validate, resubmit, cancel, priority), queue/worker status, and lab health. Minor gaps exist (e.g., no device CRUD, no test definition management), but the essential user-facing operations are present.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers