Skip to main content
Glama

Oneview List Enclosures

oneview_list_enclosures
Read-onlyIdempotent

List HPE Synergy enclosures to retrieve model, serial, status, firmware baseline, populated bays, Composer modules, power capacity, PSU health, and failed fans.

Instructions

Synergy frames / enclosures: model, serial, status, firmware baseline, populated bays, Composer modules, power capacity and allocation, PSU status and failed fans.

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_enclosures"
  }
}

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

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds no behavior beyond annotations — no note on what happens when no appliance exists, whether the first-appliance fallback is silently assumed, or how many enclosures may come back. It effectively restates the payload shape, which the output schema already provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short — one sentence fragment — so nothing is wasted, but the terseness comes at the cost of specification rather than from disciplined editing. It is not front-loaded with a purpose statement, opening instead with a raw attribute list.

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 a rich annotation set, 100% schema coverage, an output schema and a single optional parameter, the definition is minimally sufficient to call the tool correctly. However, for a read tool with many sibling list/get variants, the absence of any routing guidance leaves an agent guessing when enclosure data is the right target.

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?

There is a single optional parameter with 100% schema description coverage, including the default-to-first-appliance behavior, so the schema does the work. The description adds nothing to the meaning of 'appliance', leaving the baseline of 3 appropriate.

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

Purpose3/5

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

The description is a noun-phrase enumeration ('Synergy frames / enclosures: model, serial, status, firmware baseline...') rather than a verb-led statement of what the tool does. The resource is identifiable from the name and the listed attributes, but an agent must infer that this is a list/read operation rather than a detail fetch or inventory mutation. It is distinguishable from siblings by domain (enclosures vs. servers/interconnects), but only weakly.

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?

No guidance on when to use this tool versus alternatives such as oneview_get_appliance or the com_list_* siblings, and no exclusions or prerequisites. The only usage-relevant instruction (omit the appliance argument to use the first one) lives in the schema, not the description.

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