Skip to main content
Glama

Get Health

get_health
Read-onlyIdempotent

Retrieve overall and per-subsystem health for an HPE ProLiant server via iLO, including processors, memory, storage, network, fans, power supplies, temperatures, and redundancy status.

Instructions

Overall and per-subsystem health (processors, memory, storage, network, fans, power supplies, temperatures) plus fan / power-supply redundancy.

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

Input Schema

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. The description adds scope information (which subsystems and redundancy are reported) but nothing about latency, prerequisites such as the server being reachable, or failure behavior, so it adds only modest value beyond the structured data.

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?

A single front-loaded sentence with the resource named first and the subsystem list following. The parenthetical enumeration is somewhat long but every item conveys real coverage, so nothing is wasted.

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?

An output schema exists so return structure needn't be explained, annotations cover the safety profile, and the parameter is fully documented in schema. The description adequately conveys what domain of data is returned for a simple one-parameter read tool; only explicit routing guidance 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?

Schema description coverage is 100% with a single parameter whose schema description already explains it must come from list_servers or be an iLO host/IP. The description adds no further meaning about the parameter, which is the appropriate baseline when the schema does the work.

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 concrete resource ('overall and per-subsystem health') and enumerates the covered subsystems (processors, memory, storage, network, fans, power supplies, temperatures), which lets an agent tell it apart from per-component siblings like get_processors or get_memory. It stops short of explicitly stating it is the aggregate/summary view, relying on the enumeration to imply that.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the broad health overview versus the narrower per-subsystem tools, and the mention of redundancy checks hints at a diagnostic use case. There is no explicit when-to-use, when-not-to-use, or named alternative.

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