Skip to main content
Glama
RedHatInsights

Red Hat Lightspeed MCP

Official
by RedHatInsights
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Active Advisor Recommendations for Account

advisor__get_active_rules
Read-onlyIdempotent

Get active Advisor Recommendations affecting system health, security, or performance.

Instructions

Get active Advisor Recommendations affecting system health, security, or performance.

Lists omit playbooks; use get_rule_details for remediation. impacting=true (default) is usually preferred; impacting=false returns the global catalog.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort fields; prefix '-' for descending. Default: -total_risk.-total_risk
tagsNoTags as namespace/key=value, comma-separated (impacting=true only).
limitNoPage size (max 20).
groupsNoWorkspace names, comma-separated (impacting=true only).
impactNoComma-separated impact IDs 1-4 (see toolset instructions).
offsetNoPagination offset.
rebootNoOnly recommendations that require a reboot to fix.
categoryNoComma-separated category IDs 1-4 (see toolset instructions).
incidentNoOnly recommendations that cause incidents.
impactingNoOnly recommendations currently impacting systems.
likelihoodNoComma-separated likelihood IDs 1-4 (see toolset instructions).
has_automatic_remediationNoOnly recommendations with an automatic remediation playbook.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv0.0.25
    • changedInput schema / properties / category / description
      Previous value: -"Recommendation category filter as comma-separated string, Example: '1,2,3'. Accepted values: 1 (Availability), 2 (Security), 3 (Stability), 4 (Performance). "New value: +"Comma-separated category IDs 1-4 (see toolset instructions)."
    • changedInput schema / properties / groups / description
      Previous value: -"Filter based on workspace names. Comma separated list of workspace names.Used only when impacting=True. Example: 'workspace1,workspace2'"New value: +"Workspace names, comma-separated (impacting=true only)."
    • changedInput schema / properties / has_automatic_remediation / description
      Previous value: -"Only show recommendations that have a playbook for automatic remediation."New value: +"Only recommendations with an automatic remediation playbook."
    • changedInput schema / properties / impact / description
      Previous value: -"Impact 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."New value: +"Comma-separated impact IDs 1-4 (see toolset instructions)."
    • changedInput schema / properties / impacting / description
      Previous value: -"Only show recommendations currently impacting systems."New value: +"Only recommendations currently impacting systems."
    • changedInput schema / properties / incident / description
      Previous value: -"Only show recommendations that cause incidents."New value: +"Only recommendations that cause incidents."
    • changedInput schema / properties / likelihood / description
      Previous value: -"Likelihood 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."New value: +"Comma-separated likelihood IDs 1-4 (see toolset instructions)."
    • changedInput schema / properties / limit / description
      Previous value: -"Pagination: Maximum number of results per page."New value: +"Page size (max 20)."
    • changedInput schema / properties / offset / description
      Previous value: -"Pagination offset to skip specified number of results. Used with limit."New value: +"Pagination offset."
    • changedInput schema / properties / reboot / description
      Previous value: -"Filter recommendations that require a reboot to fix."New value: +"Only recommendations that require a reboot to fix."
    • changedInput schema / properties / sort / description
      Previous value: -"Sort 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."New value: +"Sort fields; prefix '-' for descending. Default: -total_risk."
    • changedInput schema / properties / tags / description
      Previous value: -"Filter 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'"New value: +"Tags as namespace/key=value, comma-separated (impacting=true only)."
  2. First observedv0.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare the safe read profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds genuinely new behavior: list results omit playbooks (i.e., the payload is intentionally partial), and impacting=false switches the result set from 'affecting my systems' to the global catalog. Pagination limits are left to the schema.

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?

Three short sentences, zero waste: purpose first, then the sibling pointer, then the default-parameter note. Front-loaded and scannable.

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?

An output schema exists and all 12 parameters are documented at 100%, so the description need not restate return values or filter syntax. What it does provide (routing, default preference, playbook omission) covers the main decision points. Minor gap: no hint about pagination behavior across the 12 filter parameters.

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 description coverage is 100%, so baseline is 3. The description goes beyond the schema by explaining the practical preference for the default 'impacting=true' and the semantic shift when it is set false (global catalog rather than per-system impact), which the schema's terse one-liner does not convey.

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?

States a specific verb and resource ('Get active Advisor Recommendations') plus the domain it covers ('system health, security, or performance'). It also carves itself apart from the closest sibling by naming get_rule_details for remediation, so an agent can distinguish it without opening either schema.

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?

Explicitly routes the agent: 'use get_rule_details for remediation' and 'impacting=true (default) is usually preferred; impacting=false returns the global catalog'. That gives clear when-to-use guidance for the key filter. It does not cover the other advisor siblings (get_hosts_hitting_a_rule, get_recommendations_stats), so it stops short of a full when/when-not map.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools