Skip to main content
Glama
nokia

Redfish MCP Server

by nokia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List Discovered Servers

list_discovered_servers

Lists discovered Redfish server candidates so you can review available systems before configuring them. Returns an informational list of unmanaged servers for further action.

Instructions

List discovered Redfish server candidates for review.

Returns: list: A list of discovered Redfish server candidates. These candidates are informational only and are not managed unless explicitly configured.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "items": {},
-      "type": "array"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Addedv0.4.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It explicitly discloses that the returned candidates are informational only and not managed, implying a read-only, non-mutating operation. It does not mention authentication or rate limits, but for a zero-parameter listing tool this is adequate, and it adds the key non-management context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

The description is short and front-loaded with the main action. The Returns block adds useful behavioral context about candidates being informational and unmanaged. There is minor redundancy in repeating 'discovered Redfish server candidates,' but no filler or unnecessary detail.

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 zero-parameter list operation, the description adequately covers what the tool returns, the status of those items, and the fact that they are for review. It does not specify item fields, but no output schema exists and the return type 'list' is stated. An explicit pointer to list_servers for managed servers would improve completeness, but the 'not managed' phrasing largely covers the distinction.

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

Parameters4/5

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

The tool has zero parameters, so the baseline of 4 applies. There are no parameter semantics to clarify, and the description appropriately focuses on the return value and purpose.

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 states a specific verb and resource: 'List discovered Redfish server candidates for review.' The word 'discovered' distinguishes it from the sibling 'list_servers', and the caveat that candidates are 'not managed unless explicitly configured' further clarifies its unique role.

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 gives clear context: this tool is for reviewing unmanaged discovered candidates, not for managing servers. The phrase 'informational only and are not managed unless explicitly configured' implies when to use this over list_servers. However, it does not explicitly name sibling alternatives or provide a direct when-not-to-use statement.

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