Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official

Get Application Streams relevant to the requester's inventory (includes lifecycle/support dates).

planning__get_relevant_appstreams
Read-onlyIdempotent

Retrieve inventory-relevant application streams with support dates. Filter by RHEL version and include related streams for upgrade planning.

Instructions

Get Application Streams relevant to the requester's inventory (includes lifecycle/support dates).

🟢 CALL IMMEDIATELY - No information gathering required.

Use this tool when the user asks about Application Streams in their environment (inventory, hosts, systems...), such as: "Which app streams are we running on RHEL 9?" "What successor app streams could we move to from our current streams?"

Use this tool over get_appstreams_lifecycle when the user asks about their inventory, hosts, systems...

If the question is scoped to a specific RHEL major or minor, set major (and optionally minor) so that relevance is computed only from systems on that version.

If the user wants only streams currently running (what is installed/in use in inventory), set include_related=false. If the user asks whether newer versions exist, wants upgrade recommendations, or wants successor streams to consider, set include_related=true and review entries where related=true as potential candidates.

If the user needs an exhaustive catalog view of all streams available for a given component (e.g., "list all Node.js streams across RHEL 8/9/10"), use get_appstreams_lifecycle.

The backend computes relevance based on actual host data in the user's inventory. This tool does not perform any client-side filtering; all evaluation is performed by the backend.

Returns: str: A JSON-encoded response object containing: - meta: Metadata including: - count (int): Number of records returned. - total (int): Total number of matching records. - data: A list of Application Stream records relevant to the user's inventory. Each record contains: - name (str): Technical package or module name. - display_name (str): Human-friendly display name. - application_stream_name (str): Application Stream name. - stream (str): Stream identifier or version. - start_date (str | null): Planned start date (ISO format). - end_date (str | null): Planned end-of-life date (ISO format). - support_status (str): Support status (e.g. 'Supported', 'Retired'). - os_major (int | null): RHEL major version. - os_minor (int | null): RHEL minor version. - related (bool): Indicates if this is a related/successor stream (true) or currently in use (false).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
majorNoRestricts relevance evaluation to systems running this RHEL major version.
minorNoUsed together with major to further restrict relevance evaluation to a specific minor version. Requires major to be specified.
include_relatedNoIf true, returns streams currently used plus related/successor streams. If false, returns only streams currently used in inventory.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description adds context beyond annotations: explains that relevance is computed backend based on actual host data, no client-side filtering. This aligns with readOnlyHint and idempotentHint. No contradiction.

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?

Well-structured and front-loaded: starts with 'CALL IMMEDIATELY,' then usage scenarios, parameter instructions, and output schema. Every section serves a purpose; no wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (inventory-based relevance, lifecycle dates, sibling tool), the description fully covers purpose, usage, parameters, and output schema. No gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 100% schema coverage, the description enriches parameter meaning: major/minor restrict relevance to specific RHEL versions, include_related distinguishes current usage vs. upgrade recommendations. Provides concrete guidance that the schema alone doesn't capture.

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 the tool retrieves relevant Application Streams from the user's inventory, including lifecycle/support dates. It distinguishes itself from the sibling tool `get_appstreams_lifecycle` by specifying it focuses on inventory relevance vs. an exhaustive catalog view.

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?

Provides explicit guidance: 'CALL IMMEDIATELY - No information gathering required,' example queries, when to use vs. lifecycle tool, and how to set parameters for scoping (major/minor) and include_related. Also explains when not to use (exhaustive catalog).

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