Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official
by RedHatInsights
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

inventory__load_inventory_dashboard

Read-only

Display fleet inventory in an interactive dashboard. Filter hosts by display name, FQDN, tags, provider, or workspace to locate and view managed systems.

Instructions

Show, list, or display fleet inventory in an interactive dashboard.

PREFER this tool over list_hosts whenever the user wants to see, show, list, or display hosts or fleet inventory. Use list_hosts only when you need the raw data for analysis or processing. The dashboard fetches data directly from the server. All filter parameters are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fqdnNoFilter by FQDN.
pageNoPage number.
tagsNoFilter by tags.
order_byNoSort field (display_name, updated, created).
per_pageNoNumber of hosts per page.
order_howNoSort direction (ASC or DESC).ASC
stalenessNoFilter by staleness status.
display_nameNoFilter by display name.
workspace_idNoFilter by workspace ID (UUID). Prefer this over workspace_name.
provider_typeNoFilter by provider type (aws, azure, gcp).
hostname_or_idNoFilter by display_name, fqdn, or id.
workspace_nameNoFilter by workspace name. Names can be duplicated.
registered_withNoFilter by reporter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.0.16
    • addedInput schema / properties / workspace_id
      Added value: +{
+  "default": "",
+  "description": "Filter by workspace ID (UUID). Prefer this over workspace_name.",
+  "type": "string"
+}
    • addedInput schema / properties / workspace_name
      Added value: +{
+  "default": "",
+  "description": "Filter by workspace name. Names can be duplicated.",
+  "type": "string"
+}
  2. Addedv0.0.9

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark the tool read-only; the description adds meaningful behavioral context: the dashboard fetches data directly from the server and all filter parameters are optional. This goes beyond the schema and annotation without contradicting them, though it does not detail the output format or pagination behavior.

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 short, front-loaded with the core purpose, and every sentence earns its place. The preference rule, alternative usage, and key invocation note are presented cleanly without 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?

For a 13-parameter read-only dashboard tool with no output schema, the description covers purpose, selection criteria, data source, and parameter optionality. It could more explicitly describe what the returned dashboard or response looks like, but the guidance is otherwise sufficient for correct invocation.

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?

Schema description coverage is 100%, so the schema already documents all 13 parameters. The description adds only a general statement that all filter parameters are optional, which does not provide deeper per-parameter meaning beyond what the schema already contains.

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 uses specific verbs ('show, list, or display') tied to a concrete resource ('fleet inventory in an interactive dashboard'). It also names the sibling it is not (list_hosts), making the tool's distinct role clear.

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

Usage Guidelines5/5

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

Explicitly states when to prefer this tool over list_hosts ('whenever the user wants to see, show, list, or display hosts or fleet inventory') and when to use the alternative ('only when you need the raw data for analysis or processing'). This is unambiguous guidance.

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