Skip to main content
Glama
Sign In
proliant-mcp

proliant-mcp

by hjma29
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Storage

get_storage
Read-onlyIdempotent

Retrieve HPE ProLiant storage inventory from iLO via Redfish, including controller firmware, physical drive details, and logical volumes/RAID for a specified server.

Instructions

Storage subsystems: controllers (model, firmware), physical drives (model, media, capacity, serial, firmware, bay) and logical volumes / RAID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>"
    },
    "name": "get_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYesServer name from list_servers (or its iLO host/IP).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/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 covered. The description adds value by disclosing exactly which storage entities and attributes are returned, which is behavior beyond annotations. It says nothing about failure modes (e.g., servers without a storage controller) or pagination, which leaves some gaps.

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 compact sentence with no filler; the entity list is front-loaded and every element corresponds to real returned data. It loses a point only because it is a bare fragment rather than a statement of what the tool does.

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

Completeness4/5

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

With an output schema present, return-shape explanation is unnecessary, and annotations carry the safety profile; the one required parameter is fully documented in the schema. For a single-parameter read tool this is close to sufficient, with only usage routing 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?

The tool has a single parameter with 100% schema description coverage that already explains 'server' as a name from list_servers or an iLO host/IP. The description adds no additional meaning about that parameter, so the baseline of 3 is correct.

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 the resource ('Storage subsystems') and enumerates its contents (controllers with model/firmware, physical drives with model/media/capacity/serial/firmware/bay, logical volumes/RAID). However, it is a noun-phrase fragment with no verb, so the action ('retrieve/report') is left implicit, and it does not distinguish itself from inventory siblings like get_firmware_inventory, which likely reports overlapping controller/drive firmware data.

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 stated prerequisites, and no mention of alternatives or exclusions. The agent must infer from the sibling list that this is the per-server storage counterpart to get_firmware_inventory or get_health.

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

Deploy Server

Other Tools