Skip to main content
Glama
Sign In
mcp-redfish

mcp-redfish

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

reset_manager

Restart a BMC manager (iDRAC, iLO, XCC) using graceful or force reset. Temporarily disconnects the BMC to apply the reset.

Instructions

Reset (restart) the BMC manager. Uses GracefulRestart by default. This will temporarily disconnect the BMC.

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": {
      "manager_id": "<manager_id>"
    },
    "name": "reset_manager"
  }
}

Input Schema

NameRequiredDescriptionDefault
manager_idYesManager ID (e.g. 'iDRAC.Embedded.1', 'BMC'). Use list_managers to find IDs.
reset_typeNoReset type: GracefulRestart (default, orderly shutdown) or ForceRestart (hard reset)GracefulRestart

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden. It discloses the default reset type (GracefulRestart) and the key side effect (temporary disconnect). This goes beyond the basic operation and gives the agent a warning about the impact.

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

Conciseness5/5

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

The description is compact: three short sentences, each adding value. It front-loads the action and includes necessary caveats without any filler.

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?

Given the tool has only two parameters and no output schema, the description covers the operation, default behavior, and the critical consequence. It is sufficient for an agent to select and invoke the tool correctly.

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%, so the baseline is 3. The description only repeats the default 'GracefulRestart' which is already in the schema's default field, and adds no extra meaning for manager_id or reset_type.

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

Purpose5/5

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

The description states 'Reset (restart) the BMC manager.' This is a specific verb-resource pair. It is clearly distinct from sibling read/list tools, and the parenthetical 'restart' clarifies the action.

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

Usage Guidelines4/5

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

The description provides clear context: it's the reset operation for the BMC manager, and warns that it will temporarily disconnect. However, it does not explicitly mention alternatives or when-not-to-use scenarios, though no alternatives exist among siblings.

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