Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official

Get Detailed System Information for Advisor Recommendation

advisor__get_hosts_details_for_rule
Read-onlyIdempotent

Retrieve detailed information about RHEL systems impacted by a specific Advisor recommendation, including system details and severity hit counts.

Instructions

Get detailed information about RHEL systems affected by a specific Advisor Recommendation.

Returns paginated system details with comprehensive information about each affected system, including system identification, impact metrics, RHEL version, and last seen timestamps. Each system entry contains hit counts categorized by severity level and incident status.

Call examples: Standard call: {"rule_id": "xfs_with_md_raid_hang|XFS_WITH_MD_RAID_HANG_ISSUE_DEFAULT_KERNEL"} With pagination: {"rule_id": "rule_id", "limit": 20, "offset": 0} Filter by RHEL version: {"rule_id": "rule_id", "rhel_version": "9.4"} Combined filters: {"rule_id": "rule_id", "limit": 50, "offset": 20, "rhel_version": "8.9"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rule_idYesRecommendation identifier in format: rule_name|ERROR_KEY.
limitNoPagination: Maximum number of results per page.
offsetNoPagination offset to skip specified number of results. Used with limit.
rhel_versionNoFilter systems by RHEL version. Accepts a comma-separated string or a list. Allowed values: 6.0-6.10, 7.0-7.10, 8.0-8.10, 9.0-9.8, 10.0-10.2. Example: '9.3,9.4,9.5'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, and no destructive action. The description adds value by detailing pagination, returned fields (system identification, impact metrics, RHEL version, hit counts, incident status), and no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the main verb and resource, followed by details and examples. It is structured but slightly wordy; could be more concise.

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 presence of an output schema, the description adequately covers the return content and provides examples for common use cases, making it complete for the tool's purpose.

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?

With full schema coverage, baseline is 3. The description provides concrete call examples showing parameter combinations (pagination, filtering) and usage patterns, adding meaning beyond the schema.

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 it gets detailed information about RHEL systems affected by an Advisor Recommendation. It uses specific verbs and resource, but does not explicitly differentiate from the sibling tool advisor__get_hosts_hitting_a_rule.

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

Usage Guidelines3/5

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

The description provides usage examples and implies when to call this tool, but does not explicitly state when not to use it or name alternatives like the sibling tool.

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