idrac_boot_settingsRetrieve the server's boot mode (UEFI or BIOS), boot order, and available one-time boot override targets such as PXE, virtual CD, or BIOS setup.
Show the boot mode (UEFI or BIOS), the boot order, and any one-time boot override with the targets that can be used for it (PXE, virtual CD, BIOS setup, ...).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by enumerating what is returned (boot mode, boot order, override targets such as PXE, virtual CD, BIOS setup), which is not in any structured field.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence that puts the primary content (boot mode, boot order) ahead of the secondary detail (override targets). Slightly list-dense with the parenthetical examples, but nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no input parameters and no output schema, the description must carry the return-value burden, and it does so by naming the three pieces of information returned. Adequate for the tool's simplicity, with only the sibling differentiation left unaddressed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4. The description correctly implies a no-argument inspection call and does not invent parameter semantics that don't exist.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb 'Show' and enumerates the exact resources returned: boot mode (UEFI/BIOS), boot order, and one-time boot override with targets. Clear on its own, but does not distinguish itself from the nearby idrac_bios_attributes sibling, which an agent could plausibly confuse with boot configuration.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied by the read-only 'Show' framing; there is no explicit when-to-use or when-to-prefer-idrac_bios_attributes guidance. An agent must infer that this is the boot-configuration inspection call rather than the general BIOS attribute call.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.