Skip to main content
Glama

get_alert_recommendations

Read-onlyIdempotent

Retrieve prioritized recommendations for a specific alert by resolving its alert definition, including actionable steps and priority levels.

Instructions

[READ] Get the prioritized recommendations for one alert — what Aria suggests doing about it — by resolving the alert to its alert definition and the recommendation text.

Returns alert_id, alert_name, criticality, alert_definition_id, state_severity, status, recommendations (each: id, priority — lower is more important, description, action, lookup) and note. status: "found"; "partial" (some text could not be read — ids and priorities are still listed, description null means unknown, not blank); "none_defined" (the definition defines none — recommendations is []); "unknown" (the definition could not be read — recommendations is null and must NOT be reported as "no recommendations"). An unreadable alert is an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoAria target name from config; default when omitted.
alert_idYesThe alert UUID from list_alerts (not the resource UUID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.15.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds critical behavioral details beyond that: the four possible statuses ('found', 'partial', 'none_defined', 'unknown') and their exact implications for the 'recommendations' field (e.g., null vs []). It also warns that 'unknown' must not be interpreted as 'no recommendations'.

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?

The description is dense but well-organized. It front-loads the purpose, then details the return fields and statuses in a structured way. Every sentence adds necessary information, and there is no fluff.

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?

Despite no output schema, the description fully specifies return fields, statuses, and their meanings. It covers edge cases and potential errors, making it complete for an agent to understand what to expect. The only minor gap is the 'target' parameter's usage, but it is well covered by the schema.

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 the schema already explains both parameters. The description adds crucial semantics for 'alert_id' by specifying it must be an alert UUID from list_alerts (not a resource UUID), which is not in the schema and prevents a common mistake.

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 states a specific verb ('get'), a clear resource ('recommendations for one alert'), and explains the mechanism ('resolving the alert to its alert definition'). It distinguishes itself from siblings like 'investigate_alert' and 'list_rightsizing_recommendations' by focusing on Aria's prioritized recommendations.

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 clearly indicates when to use this tool (for getting Aria's specific recommendations for a single alert) but does not explicitly exclude alternatives or mention when not to use it. However, the purpose is distinct enough that an agent can infer usage.

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