Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official

Get Active Advisor Recommendations for Account

advisor__get_active_rules
Read-onlyIdempotent

Retrieve active Advisor recommendations to identify issues affecting system availability, stability, performance, or security. Filter by impact, likelihood, category, and more to find critical problems.

Instructions

Get active Advisor Recommendations for your account that help identify issues affecting system availability, stability, performance, or security.

Use filters to find recommendations by impact level, likelihood, systems affected, workspace, tags, and automatic remediation availability. Higher impact/likelihood values indicate more critical issues.

Call examples: Standard call: {"impacting": true, "offset": 0, "limit": 20} High risk only: {"impacting": true, "impact": "3,4", "likelihood": "3,4"} Pagination: {"offset": 20, "limit": 20} With automatic remediation: {"has_automatic_remediation": true} Security and Performance categories: {"category": "2,4"} Reboot required: {"reboot": true} Sorted by total risk: {"sort": "-total_risk"} For workspaces 'workspace1': {"impacting": true, "groups": "workspace1"} For systems tagged 'database-servers': { "impacting": true, "tags": ["insights-client/group=database-servers"] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
impactingNoOnly show recommendations currently impacting systems.
incidentNoOnly show recommendations that cause incidents.
has_automatic_remediationNoOnly show recommendations that have a playbook for automatic remediation.
impactNoImpact level filter as comma-separated string, Example: '1,2,3'. Accepted values: 1 (Low), 2 (Medium), 3 (High), 4 (Critical). Use only these exact values: 1, 2, 3, or 4.
likelihoodNoLikelihood level filter as comma-separated string, Example: '1,2,3'. Accepted values: 1 (Low), 2 (Medium), 3 (High), 4 (Very High). Use only these exact values: 1, 2, 3, or 4.
categoryNoRecommendation category filter as comma-separated string, Example: '1,2,3'. Accepted values: 1 (Availability), 2 (Security), 3 (Stability), 4 (Performance).
rebootNoFilter recommendations that require a reboot to fix.
sortNoSort field as comma-separated string. Example: '-total_risk,rule_id'. Available fields: category, description, impact, impacted_count, likelihood, playbook_count, publish_date, resolution_risk, rule_id, total_risk. Use '-' prefix for descending order.-total_risk
offsetNoPagination offset to skip specified number of results. Used with limit.
limitNoPagination: Maximum number of results per page.
groupsNoFilter based on workspace names. Comma separated list of workspace names.Used only when impacting=True. Example: 'workspace1,workspace2'
tagsNoFilter based on system tags. Accepts a single tag or a comma-separated list.Used only when impacting=True. Tag format: 'namespace/key=value'. Example: 'satellite/group=database-servers,insights-client/security=strict'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds context about the type of issues addressed (availability, stability, etc.) and includes call examples, but does not disclose additional behavioral traits beyond what annotations cover.

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 well-structured with a clear opening statement, filter explanation, and numerous examples. It is front-loaded but could be slightly more concise without losing the comprehensive examples.

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 has 12 parameters with full schema descriptions and an output schema exists, the description covers the tool's purpose, filtering options, pagination, and provides concrete examples. No significant gaps are present.

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 coverage is 100%, so baseline is 3. The description adds value through multiple call examples (e.g., filtering by impact and likelihood, pagination) that illustrate parameter usage patterns beyond the schema descriptions.

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 'Get active Advisor Recommendations' with a specific verb and resource. It mentions the purpose (identify issues affecting availability, stability, performance, security) and differentiates from sibling tools by focusing on active rules.

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 call examples for various use cases (impacting, high risk, pagination, etc.), which guide usage. However, it does not explicitly state when not to use this tool or compare it to alternatives like advisor__get_rule_details.

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