Skip to main content
Glama
Sign In
mcp-redfish

mcp-redfish

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

set_power_state

Change a computer system's power state remotely using Redfish BMC. Supports power on, off (graceful or forced), restart, NMI, and power button simulation.

Instructions

Change the power state of a computer system. Supported reset types: On, ForceOff, GracefulShutdown, GracefulRestart, ForceRestart, Nmi, PushPowerButton.

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": {
      "system_id": "<system_id>",
      "reset_type": "<reset_type>"
    },
    "name": "set_power_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
system_idYesSystem ID (e.g. '1', 'System.Embedded.1'). Use list_systems to find IDs.
reset_typeYesReset type: On (power on), ForceOff (hard off), GracefulShutdown (soft off), GracefulRestart (soft reboot), ForceRestart (hard reboot), Nmi (non-maskable interrupt), PushPowerButton (simulate button press)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

There are no annotations, so the description must disclose behavioral traits. It lists supported reset types but does not warn about destructive effects (ForceOff, ForceRestart), potential data loss, or prerequisites for graceful operations. This is a safety-relevant tool, so the omission is significant.

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?

Two sentences, front-loaded with the action and resource. The list of reset types is concise, though duplicated in schema, but its placement in the description enables quick agent scanning without parameter lookup.

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

Completeness2/5

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

For a power-control tool with no output schema, the description is too thin. It lacks safety warnings, expected outcomes, and any mention of when to use which reset type (beyond the schema's one-line meanings). It is not complete enough for an agent to safely invoke this tool without additional context.

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 coverage is 100% and both parameters have detailed descriptions in the schema, including enum value explanations. The description adds no extra parameter meaning beyond the schema; it only repeats the enum list, which is redundant but not harmful.

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?

States a clear verb ('Change') and resource ('power state of a computer system'), with a specific list of supported reset types. This distinguishes it from sibling tools like reset_manager, which targets manager resources.

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?

Provides clear context: it is for computer systems and enumerates valid reset types. However, it does not explicitly mention exclusions (e.g., 'use reset_manager for manager power') or alternative tools, so it stops short of full when/when-not guidance.

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