Skip to main content
Glama

Oneview List Firmware Baselines

oneview_list_firmware_baselines
Read-onlyIdempotent

Lists firmware baselines uploaded to OneView, including SPP and Synergy Service Packs, for a specified or default appliance.

Instructions

Firmware baselines (SPP / Synergy Service Packs) uploaded to OneView, 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": "oneview_list_firmware_baselines"
  }
}

Input Schema

NameRequiredDescriptionDefault
applianceNoOneView appliance name from list_servers; omit to use the first one.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.6.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered elsewhere. The description adds one genuine behavioral detail not in the annotations: results are returned newest first. It says nothing about whether all baselines are returned or how the appliance scope affects results.

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?

One short sentence fragment with zero filler, and the most useful fact (newest first) is placed after the resource identification. It is efficient, though the missing verb makes it read more like a label than a directive.

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?

For a read-only single-optional-parameter listing tool with full schema coverage, a complete output schema and covering annotations, the description supplies what is needed to call it correctly. Return-value details are handled by the output schema, so nothing essential is missing.

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?

With a single optional parameter and 100% schema description coverage, the schema already explains the appliance argument and its 'omit to use the first one' default. The description adds no further meaning about the parameter, which is the baseline expectation at full coverage.

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 the concrete resource (firmware baselines, clarified as SPP / Synergy Service Packs) and the ordering, on top of the tool name's 'list' verb. It does not distinguish itself from the sibling com_list_firmware_bundles, which appears to cover a similar domain, so an agent gets a clear purpose but no sibling differentiation.

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 statement of when to use this tool, no prerequisites (e.g., when a baseline must have been uploaded), and no pointer to alternatives such as com_list_firmware_bundles or get_firmware_inventory. The agent must infer usage entirely from the name and resource.

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