Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official

inventory__list_hosts

Read-only

Queries Red Hat Inventory to list hosts with filtering by hostname, tags, staleness, and other attributes. Supports sorting and pagination.

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
NameRequiredDescriptionDefault
hostname_or_idNoFilter by display_name, fqdn, or id (case-insensitive).
display_nameNoFilter by display name (case-insensitive).
fqdnNoFilter by FQDN (case-insensitive).
tagsNoFilter by tags (e.g., 'ns1/key1=val1,ns2/key2=val2').
stalenessNoFilter by staleness status (one of 'fresh', 'stale', 'stale_warning', 'unknown').
registered_withNoFilter by reporter that registered the host.
provider_typeNoFilter by provider type (e.g., 'aws', 'azure', 'gcp').
updated_startNoFilter hosts updated after this timestamp (RFC3339).
updated_endNoFilter hosts updated before this timestamp (RFC3339).
per_pageNoNumber 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
pageNoPage number to return.
order_byNoField to sort by ('display_name', 'updated', 'created').
order_howNoSort direction ('ASC' or 'DESC').ASC

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description adds a critical behavioral trait: using per_page=10 to avoid performance degradation and context overflow. This is beyond the readOnlyHint annotation, providing actionable context about side effects and best practices.

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?

Description is two sentences with a clear critical section. No extra words, front-loaded with purpose. Every sentence earns its place.

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?

Given 13 parameters, full schema coverage, and an output schema, the description adequately covers usage with a critical note. It lacks details on pagination beyond per_page, but that is likely covered by the output schema. Overall, sufficient for an agent.

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 covers 100% of parameters. The description adds significant value for the per_page parameter by emphasizing the default and warning against increasing it unless explicitly requested. Other parameters are described only in schema, but the added guidance is substantial.

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?

Description states 'List hosts with filtering and sorting options', which is a specific verb and resource. It clearly distinguishes from sibling tools like inventory__find_host_by_name and inventory__get_host_details by indicating a listing operation with filtering.

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?

Provides explicit critical guidance on using per_page=10 first and only increasing if user explicitly asks. This is a clear usage instruction. However, it does not explicitly mention when not to use this tool versus alternatives, though siblings suggest different use cases.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RedHatInsights/insights-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server