Skip to main content
Glama

Com List Firmware Bundles

com_list_firmware_bundles
Read-onlyIdempotent

Lists available firmware bundles and patches from HPE Compute Ops Management, newest first, with optional filters for account and superseded bundles.

Instructions

Firmware bundles (SPPs and patches) available in COM, newest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "com_list_firmware_bundles"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoCOM account name from list_servers; omit to use the first one.
include_inactiveNoAlso list superseded bundles.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds two useful traits the annotations don't carry: the result ordering (newest first) and the bundle types included (SPPs and patches). It says nothing about pagination, result size, or whether inactive bundles are excluded by default at the behavioral level.

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?

A single front-loaded sentence with no filler. The parenthetical defining SPPs and patches and the trailing ordering note both earn their place.

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

Completeness3/5

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

With an output schema present, the description needn't explain return values, and the schema fully documents the two parameters. What remains missing is routing guidance among the several firmware-related siblings, which matters given how many adjacent tools exist in this catalog.

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 description coverage is 100%, and both parameters are documented in the schema itself, including the non-obvious default of using the first COM account and the meaning of include_inactive. The description adds no parameter meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (firmware bundles, clarified as SPPs and patches) and a scope (available in COM, returned newest first), so the agent knows exactly what the tool returns. It does not, however, distinguish itself from sibling firmware tools such as oneview_list_firmware_baselines or get_firmware_inventory.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance. The phrase 'available in COM' hints that this is the COM-side catalog rather than the OneView baselines or the inventory view, but the agent is left to infer that from a prepositional phrase rather than from a stated selection rule.

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