Red Hat Lightspeed MCP

Official

Overview Schema Source Related Servers Discussions Admin

inventory__list_workspace_hosts

Read-only

Retrieve all hosts assigned to a workspace by providing its workspace ID. Apply filters like FQDN, tags, or staleness to narrow down the inventory.

Instructions

List hosts that belong to a workspace.

Use list_workspaces first to obtain the workspace ID. Required permission: inventory:hosts:read (Inventory Hosts viewer).

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. 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').
`display_name`	No	Filter by display name (case-insensitive).
`workspace_id`	Yes	Workspace ID (UUID) whose hosts to list.
`hostname_or_id`	No	Filter by display_name, fqdn, or id (case-insensitive).
`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.

Addedv0.0.16Sep 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already mark the operation as read-only. The description adds useful behavioral context by stating the required permission (inventory:hosts:read) and the prerequisite workflow of calling list_workspaces first. This goes beyond the annotation and helps the agent understand access and sequencing requirements.

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 the key prerequisite and permission. Every sentence contributes necessary information with no redundancy or filler.

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 an output schema, full parameter descriptions, and a read-only annotation, the description covers the essential workflow and authorization details. It does not discuss when to prefer inventory__list_hosts over this tool, but the workspace-scoped purpose is sufficiently clear for correct invocation.

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 baseline is 3. The description adds meaning for the required workspace_id parameter by explaining how to obtain it via list_workspaces, which is beyond the schema's simple 'Workspace ID (UUID)' definition.

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 opens with 'List hosts that belong to a workspace,' which is a specific verb, resource, and scope. This clearly differentiates the tool from the sibling inventory__list_hosts, which appears to cover hosts without the workspace constraint.

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?

It explicitly instructs to use list_workspaces first to obtain the workspace ID, giving a clear prerequisite and workflow. It does not explicitly state when not to use it or name alternatives, but the usage context is clear and actionable.

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

Deploy Server