Skip to main content
Glama
Sign In
Redfish MCP Server

Redfish MCP Server

by carlosedp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

redfish_get_audit_logs

Retrieve audit logs from Redfish-enabled hardware for security monitoring and compliance. Filter by log type and limit results as needed.

Instructions

Get comprehensive audit logs for security and compliance monitoring

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": "redfish_get_audit_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
log_typeNoAll

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only the purpose and does not mention read-only behavior, pagination, default limits, or any side effects. 'Comprehensive' hints at broad coverage but lacks specifics about what the tool actually does.

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, clear sentence with no wasted words. It is front-loaded with the action and resource, making it easy to process quickly.

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

Completeness3/5

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

The description is minimal but adequate for a simple read tool with two optional parameters and no output schema. However, it omits critical details about parameter semantics and usage context, making it insufficient for an agent to fully understand filtering or limits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has two parameters (limit, log_type) with no descriptions, and the tool description offers zero additional meaning. The phrase 'comprehensive' does not bridge the gap, leaving the agent without any guidance on how limit or log_type affect the operation.

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 tool gets 'comprehensive audit logs' for security and compliance monitoring, using a specific verb and resource. However, it does not explicitly differentiate from the sibling tool 'redfish_get_manager_logs', which could be confused for audit logs.

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?

The description provides no guidance on when to use this tool versus alternatives, such as redfish_get_manager_logs or redfish_clear_logs. The phrase 'for security and compliance monitoring' implies a context but does not offer explicit exclusions or alternative references.

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