lava-mcp

Overview Schema Source Related Servers Discussions Admin

get_qdl_info

Summarizes a device's QDL and flash capability, including supported deploy methods and boot parameters, for Qualcomm boards before flashing.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "hostname": "<hostname>"
    },
    "name": "get_qdl_info"
  }
}

Input Schema

Name	Required	Description	Default
`hostname`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses that the tool derives information from 'the device's rendered configuration' and specifies the nature of returned data. While it does not explicitly state read-only behavior, this is implied by the 'summarise' verb and lack of destructive hints.

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?

Two sentences with no filler. The first sentence states the purpose, and the second elaborates on when and what. Every word adds value.

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 single-parameter tool with no output schema, the description sufficiently covers inputs and outputs. It could optionally note that the tool is read-only, but that is implied.

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 coverage is 0% and the sole parameter 'hostname' is not described in the description. However, the tool name and context ('device') strongly imply that hostname identifies a device, providing partial meaning. Explicit clarification would improve clarity.

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 uses a specific verb 'Summarise' and clearly identifies the resource as 'a device's QDL/flash capability'. It lists concrete outputs: whether qdl is supported, deploy/boot method parameters, and available methods. This distinguishes it from siblings like get_device which gives generic device info.

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?

The description explicitly states 'Useful before flashing a Qualcomm board' which provides clear context for when to invoke the tool. It does not list when not to use or alternative tools, but the guidance is strong and scoped.

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