cimc-mcp

set_bios_setting

Modify BIOS configuration settings on Cisco C-Series servers through CIMC. Change token values to customize server hardware behavior, requiring reboot to apply changes.

Instructions

Modify a BIOS token value. Use get_bios_settings first to discover available tokens, class names, and attribute names. Requires server reboot to take effect.

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": {
      "tokenDn": "<tokenDn>",
      "className": "<className>",
      "attributeName": "<attributeName>",
      "value": "<value>",
      "confirm": "<confirm>"
    },
    "name": "set_bios_setting"
  }
}

Input Schema

Name	Required	Description
`tokenDn`	Yes	Full DN of the BIOS token, e.g. sys/rack-unit-1/bios/bios-settings/SelectMemory-RAS-configuration
`className`	Yes	BIOS token class name, e.g. biosVfSelectMemoryRASConfiguration
`attributeName`	Yes	Attribute to set, e.g. vpSelectMemoryRASConfiguration
`value`	Yes	New value for the token
`confirm`	Yes	Must be true to modify BIOS settings

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 11, 2026

TDQS

A4.4/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 full burden of behavioral disclosure. It effectively discloses critical behavioral traits: it is a mutation tool (implied by 'Modify'), requires a server reboot to take effect (a significant side effect), and has a prerequisite (using get_bios_settings first). However, it does not mention authentication needs, rate limits, or error handling, leaving 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.

Conciseness5/5

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

The description is front-loaded with the core purpose, followed by usage guidance and a critical side effect, all in three concise sentences with zero wasted words. Each sentence adds essential value: the action, prerequisite, and behavioral consequence.

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?

Given the complexity (a mutation tool with server reboot requirement), no annotations, and no output schema, the description does well by covering purpose, usage guidelines, and a key behavioral trait. However, it lacks details on return values, error conditions, or security requirements, which would be beneficial for full completeness.

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 schema description coverage is 100%, so the schema already documents all five parameters thoroughly. The description does not add any parameter-specific semantics beyond what the schema provides, such as explaining relationships between parameters or usage examples. This meets the baseline for high schema coverage.

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 clearly states the specific action ('Modify a BIOS token value') and identifies the resource ('BIOS token'), distinguishing it from sibling tools like get_bios_settings (which discovers tokens) and other read-only tools. It provides a precise verb+resource combination that is not tautological.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('Use get_bios_settings first to discover available tokens...') and provides a prerequisite action. It also distinguishes it from the sibling get_bios_settings by indicating this is for modification after discovery, offering clear contextual guidance.

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

Deploy Server