Red Hat Lightspeed MCP

Official

Overview Schema Source Related Servers Discussions Admin

inventory__list_hosts

Read-only

List hosts from Red Hat Lightspeed inventory with filtering by FQDN, tags, provider, staleness, and more. Sort results and paginate to find the exact systems you need.

Instructions

List hosts with filtering and sorting options. CRITICAL: For the 'per_page' parameter, you MUST use a value of 10 on the first call to avoid performance degradation and context overflow. Only use a larger value if the user explicitly requests to see more systems at once.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`fqdn`	No	Filter by FQDN (case-insensitive).
`page`	No	Page number to return.
`tags`	No	Filter by tags (e.g., 'ns1/key1=val1,ns2/key2=val2').
`order_by`	No	Field to sort by ('display_name', 'updated', 'created').
`per_page`	No	Number of hosts to return per page ALWAYS use the default value of 10 for the first call. This default is carefully chosen for performance and context management. Only increase this value if the user explicitly asks to see more systems at once
`order_how`	No	Sort direction ('ASC' or 'DESC').	ASC
`staleness`	No	Filter by staleness status (one of 'fresh', 'stale', 'stale_warning', 'unknown').
`updated_end`	No	Filter hosts updated before this timestamp (RFC3339).
`display_name`	No	Filter by display name (case-insensitive).
`workspace_id`	No	Filter by workspace ID (UUID). Prefer this over workspace_name; names can be duplicated.
`provider_type`	No	Filter by provider type (e.g., 'aws', 'azure', 'gcp').
`updated_start`	No	Filter hosts updated after this timestamp (RFC3339).
`hostname_or_id`	No	Filter by display_name, fqdn, or id (case-insensitive).
`workspace_name`	No	Filter by workspace name. Names can be duplicated.
`registered_with`	No	Filter by reporter that registered the host.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.0.16Sep 8, 2026

addedInput schema / properties / workspace_id

Added value: +{
+  "default": "",
+  "description": "Filter by workspace ID (UUID). Prefer this over workspace_name; names can be duplicated.",
+  "type": "string"
+}

addedInput schema / properties / workspace_name

Added value: +{
+  "default": "",
+  "description": "Filter by workspace name. Names can be duplicated.",
+  "type": "string"
+}

First observedv0.0.0May 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful behavioral context by warning about performance degradation and context overflow with larger per_page values, which goes beyond the annotation and helps the agent make safer calls.

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 compact and front-loaded with the core purpose, followed by a high-priority usage warning. Every sentence earns its place, and the critical warning is clearly separated and emphasized without redundancy in the description (the schema also repeats it, but that does not hurt this dimension).

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?

With 15 parameters but 100% schema coverage and an output schema present, the description covers the key non-obvious operational constraint (per_page). It is sufficient for correct invocation, though it could have briefly pointed to sibling tools for alternative list/find use cases to be fully complete in context.

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?

Schema description coverage is 100%, so the description does not need to re-document each parameter. It adds extra semantic value specifically for per_page by explaining the performance and context implications and the rule for changing the default, which is not present in the schema alone.

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 and resource: 'List hosts with filtering and sorting options.' This is specific and unambiguous. However, it does not explicitly distinguish itself from sibling tools like inventory__find_host_by_name or inventory__list_workspace_hosts, so it misses the top score for sibling differentiation.

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

Usage Guidelines3/5

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

The description provides strong parameter-level usage guidance by mandating per_page=10 on the first call and restricting larger values to explicit user requests. However, it gives no guidance on when to choose this tool over alternative inventory tools such as find_host_by_name or list_workspace_hosts, so the 'vs alternatives' aspect is only implied by the purpose.

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

Deploy Server