Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official

Get Application Streams lifecycle information.

planning__get_appstreams_lifecycle
Read-onlyIdempotent

Retrieve Application Streams lifecycle data for RHEL modules and packages, including support status, start and end dates, across specific or multiple major versions.

Instructions

Get Application Streams lifecycle information.

🟢 CALL IMMEDIATELY - No information gathering required.

Use this tool when the user asks about Application Streams lifecycle (modules or packages) or wants to understand what streams exist for specific RHEL versions.

Guidance:

  • For detailed lifecycle of modules/packages on a specific RHEL major, use mode="raw" and set 'major'.

  • For an overview across RHEL generations (e.g. "what nginx streams exist in 8/9/10"), use mode="streams".

  • When the user mentions a human-friendly stream name like ".NET 7", use 'application_stream_name'.

  • When the user mentions the technical module/package name, use 'name'.

  • Only use 'kind' when the user explicitly distinguishes between module and package implementations.

Returns: str: A JSON-encoded response object containing: - meta: Metadata including: - count (int): Number of records returned in this page. - total (int): Total number of matching records. - data: A list of Application Stream lifecycle records. Each record typically contains: - name (str): Technical package or module name (e.g. 'aspnetcore-runtime-8.0'). - display_name (str): Human-friendly display name (e.g. '.NET 8'). - application_stream_name (str): Application Stream name (e.g. '.NET 8', 'PostgreSQL 16', 'container-tools'). - application_stream_type (str | null): Stream type label (e.g. 'Application Stream', 'Full Life Application Stream', 'Rolling Application Stream'). - stream (str): Stream identifier or version (e.g. '8.0.13', '1.24', '1.14.0'). - start_date (str | null): Planned start date for the stream, in ISO format (YYYY-MM-DD). - end_date (str | null): Planned end-of-life date for the stream, in ISO format (YYYY-MM-DD). - impl (str): Implementation kind (e.g. 'package' or 'dnf_module'). - initial_product_version (str | null): First RHEL product version where this stream is available (e.g. '9.4', '10.0'). - support_status (str): Calculated support status (e.g. 'Supported', 'Near retirement', 'Retired'). - os_major (int | null): RHEL major version (e.g. 8, 9, 10). - os_minor (int | null): RHEL minor version where the stream first appears (e.g. 0, 4). - lifecycle (dict | null): Reserved for additional lifecycle metadata (may be null). - rolling (bool): Indicates whether this is a rolling Application Stream (True) or a fixed-lifecycle stream (False).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoMode for Application Streams lifecycle: 'raw' (per-major) or 'streams' (cross-major overview).raw
majorNoRHEL major version (e.g. '8', '9', '10'). Required when mode='raw'.
nameNoModule or package technical name filter (e.g. 'aspnetcore-runtime-7.0', 'postgresql').
application_stream_nameNoHuman-friendly stream name (e.g. '.NET 7', 'PostgreSQL 16', '1.24').
application_stream_typeNoApplication stream type (e.g. "module" or "package").
kindNoBackend kind filter, e.g. "dnf_module" or "package".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations indicate readOnly, idempotent, open world. Description consistently adds context that it's safe to call immediately and explains the return format with field details. No contradiction, and the added detail on response structure enhances transparency.

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 with clear sections (call indicator, usage guidance, parameter details, returns). Every sentence provides value; no fluff. Proper use of headings and bullet points for readability.

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 (6 parameters, output schema present), the description is exhaustive. It covers all parameter scenarios, explains the output structure with examples, and is self-sufficient. No gaps identified.

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?

Schema coverage is 100%, yet the description adds substantial meaning beyond the schema: explains the mode options, how to choose between name and application_stream_name, and when to use kind. This greatly aids correct invocation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets Application Streams lifecycle information, with verb 'Get' and specific resource. It doesn't explicitly differentiate from sibling tools like planning__get_relevant_appstreams, but the purpose is unambiguous and detailed.

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?

Excellent guidelines: includes an immediate call indicator, explicit when-to-use, and detailed parameter-specific guidance (when to use mode='raw' vs 'streams', how to use name vs application_stream_name, and when to use kind).

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