mcp-redfish

list_event_log

Fetch system event log entries from Redfish systems or BMC managers, returning severity, message, and timestamp. Automatically discovers common log paths.

Instructions

Get system event log entries from a system or BMC manager. Returns recent entries with Severity, Message, and Created timestamp. Tries common log paths automatically (SEL, System, Log1).

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": {
      "resource_type": "<resource_type>",
      "resource_id": "<resource_id>"
    },
    "name": "list_event_log"
  }
}

Input Schema

Name	Required	Description
`log_id`	No	Specific log service ID (e.g. 'Log1', 'Sel', 'System'). If omitted, auto-discovered.
`max_entries`	No	Maximum number of log entries to return (default 50)
`resource_id`	Yes	Resource ID (e.g. '1', 'System.Embedded.1', 'iDRAC.Embedded.1'). Use list_systems or list_managers.
`resource_type`	Yes	Resource type to read logs from: 'Systems' for system event log, 'Managers' for BMC/SEL log
`severity_filter`	No	Filter entries by severity level

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A4.2/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 reveals that the tool returns entries with specific fields and automatically tries common log paths (SEL, System, Log1), which is valuable for understanding its behavior. It does not explicitly state read-only semantics, but 'Get' strongly implies it. The disclosure is reasonable for a list operation.

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 three concise sentences. It front-loads the purpose, then adds return fields and auto-discovery behavior. There is no redundant information or fluff; every sentence contributes useful context.

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?

For a list tool with 5 parameters and no output schema, the description covers the key aspects: what it does, the resource types, automatic path handling, and the fields returned. It does not mention how to obtain resource IDs (though sibling tools list_systems/list_managers imply this), but the schema fills those gaps. Overall, it is sufficiently complete for the complexity level.

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 each parameter is already well-documented. The description adds minimal semantic value for parameters, mainly reinforcing the auto-discovery behavior for log_id with examples. Since the schema covers parameters thoroughly, a baseline score of 3 is appropriate; the description provides marginal extra meaning.

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 tool's function: retrieving system event log entries from a system or BMC manager. It specifies the resource type and the data returned (Severity, Message, Created timestamp), and distinguishes itself from sibling tools like clear_event_log by focusing on reading logs. The verb 'Get' is specific and the scope is well-defined.

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 makes the primary use case clear: to obtain event log entries. It also notes automatic log path discovery, which is a helpful usage hint. However, it does not explicitly mention alternatives or exclusions (e.g., when to use clear_event_log instead), though the sibling list implies such distinctions. The context is strong enough without explicit '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