cimc-mcp

get_event_log

Retrieve system event log entries from Cisco CIMC to monitor hardware events, errors, and status changes for server health management.

Instructions

Get system event log (SEL) entries from the CIMC. Shows hardware events, errors, and status changes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_event_log"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of entries to return (default 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 11, 2026

TDQS

C2.9/5.0

Behavior2/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 states what the tool does but doesn't cover important traits like whether it's read-only, requires authentication, has rate limits, or what the return format looks like (e.g., pagination, error handling). This leaves significant gaps for an agent to understand how to invoke it correctly.

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 a single, efficient sentence that front-loads the purpose and scope without unnecessary details. Every word earns its place, making it highly concise and well-structured.

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?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain behavioral aspects like safety, authentication, or return values, which are crucial for a tool that retrieves system data. This leaves the agent with insufficient context to use the tool effectively.

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 input schema has 100% description coverage, with the 'limit' parameter well-documented. The description doesn't add any parameter-specific information beyond what the schema provides, so it meets the baseline of 3 for adequate but no extra value.

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

Purpose4/5

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

The description clearly states the verb 'Get' and resource 'system event log (SEL) entries from the CIMC', specifying it shows hardware events, errors, and status changes. However, it doesn't explicitly differentiate from sibling tools like get_faults or get_server_health, which might also report errors or status.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as get_faults or get_server_health, which might overlap in reporting hardware issues. The description implies usage for hardware events but lacks explicit context or exclusions.

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

Deploy Server