list_module_packsList DLC-like AirMCP module packs and whether each pack is available in the current runtime configuration.
List DLC-like AirMCP module packs and whether each pack is available in the current runtime configuration.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| packs | Yes | ||
| active | Yes | ||
| configured | Yes |
Changes observed during successful MCP inspections.
v2.16.6Output schema / properties / packs / items / properties / installCommand / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / packs / items / properties / installCommand / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / packs / items / properties / installSpec / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / packs / items / properties / installSpec / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / packs / items / properties / installedSizeBytes / anyOfRemoved value: -[
- {
- "type": "number"
- },
- {
- "type": "null"
- }
-]Output schema / properties / packs / items / properties / installedSizeBytes / typeAdded value: +[
+ "number",
+ "null"
+]Output schema / properties / packs / items / properties / installedVersion / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / packs / items / properties / installedVersion / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / packs / items / properties / repairCommand / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / packs / items / properties / repairCommand / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / packs / items / properties / uninstallCommand / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / packs / items / properties / uninstallCommand / typeAdded value: +[
+ "string",
+ "null"
+]Output schema / properties / packs / items / properties / updateCommand / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Output schema / properties / packs / items / properties / updateCommand / typeAdded value: +[
+ "string",
+ "null"
+]v2.16.5Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Output schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"v2.14.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare a safe, idempotent, closed-world read, so the description's job is lighter. It still adds genuine behavior context: results reflect the *current runtime configuration*, so the same call can return different availability across environments — a detail nothing in the structured fields conveys.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no filler, front-loading the resource ('List ... module packs') before the qualifier about availability. Nothing could be deleted without losing information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present and rich annotations, the description need not explain return values or safety. It covers what is listed and why results are conditional; only the notion of what a 'DLC-like module pack' actually is remains slightly under-explained.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so there is no parameter semantics to document; the baseline for an empty schema is 4. The description correctly implies an unfiltered full listing rather than any scoped retrieval.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb+resource (list module packs) and adds the distinguishing scope 'whether each pack is available in the current runtime configuration'. It is clearly separable from install_module_pack and from unrelated list_* siblings, though it never explicitly contrasts itself with the installer.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied: an agent can infer it is the pre-check for install_module_pack, but the description never states when to call it, when not to, or which sibling to prefer. No prerequisites or follow-up steps are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.