Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official

inventory__list_hosts

Read-only

Retrieve a filtered, paginated list of hosts. Apply filters by hostname, tags, staleness, or provider. Sort results by display name, update, or creation time.

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
Behavior4/5

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

Annotations already declare readOnlyHint: true, indicating a safe read operation. The description adds important behavioral context beyond annotations by warning about performance degradation and context overflow with per_page values larger than 10.

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 concise with only two sentences plus a critical note. It is front-loaded with the purpose, and every sentence adds value—no wasted words.

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 the presence of an output schema, the description does not need to describe return values. It adequately covers the core functionality and critical per_page behavior. Pagination is implied but could be more explicit.

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 parameters. The description only adds emphasis on per_page usage, which is useful but not a significant addition beyond the schema.

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 clearly states 'List hosts with filtering and sorting options,' specifying the action and resource. It distinguishes from sibling tools like inventory__find_host_by_name (which searches by name) and inventory__get_host_details (which retrieves specific host info).

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 provides explicit guidance on the per_page parameter: use 10 on first call, only larger if user explicitly requests. This helps avoid performance issues. It implies the tool is for listing with options, but does not explicitly state when to use alternatives.

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