Skip to main content
Glama

Oneview List Interconnects

oneview_list_interconnects
Read-onlyIdempotent

Lists interconnect modules in HPE OneView, such as Virtual Connect and switches, with model, firmware, status, power, enclosure, hostname, and IP details for inventory and health checks.

Instructions

Interconnect modules (Virtual Connect, switches): model, firmware, status, power, enclosure, hostname and IP.

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

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. The description adds nothing beyond that — no note on scope of the listing, whether it queries the whole appliance, or how the openWorld remote call behaves.

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?

It is a single short fragment with no wasted words, but it is structured as an attribute list rather than a front-loaded purpose statement. Brevity here comes at the cost of specification rather than being earned economy.

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?

An output schema exists, so the field enumeration in the description is largely redundant, and the description omits the operational context an agent would want (what interconnects are, when this listing matters). For a simple read-only single-parameter tool, the name plus annotations plus schema make it minimally sufficient.

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?

Only one optional parameter exists and schema coverage is 100%, so the schema already explains the 'appliance' fallback behavior. The description contributes no additional meaning about the appliance parameter, so the baseline of 3 applies.

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 names a specific resource type (interconnect modules, Virtual Connect, switches) and enumerates the attributes returned, which tells an agent what data it surfaces. However, it is a noun phrase with no verb and no differentiation from siblings such as oneview_list_enclosures or oneview_list_server_hardware; the list action is only implied by the tool name.

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 when-to-use guidance, no mention of prerequisites (e.g., needing an appliance already registered), and no routing to alternatives. The only implied guidance comes from the schema's mention of 'appliance from list_servers', not from the description itself.

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