Skip to main content
Glama

List application alerts

list_application_alerts
Read-only

List the alerts of one Application. Its own alerts (own=true) watch its failed requests, p95 response time or restarts on one environment; change or remove one with update_application_alert or delete_application_alert. With environment_id, the organisation alert rules that watch that environment's clusters are listed beside them (own=false): those are the organisation's, changed with the organisation alert tools. Each alert says what it watches (says, condition), where it sends to (send_to), whether it is on, its last firing, and whether the evaluator could read it (evaluation: ok, unknown with unknown_reason, or not_evaluated before its first run). covered_by_organisation_rules is true or false only when an environment was read: null means it was not read, never that nothing watches it. Read-only. Needs alerts.read where the application is.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "application_id": "<application_id>"
    },
    "name": "list_application_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
application_idYesThe Application's id.
environment_idNoOptional. One environment of the application: lists the alerts on it and the organisation rules that watch its clusters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description goes further by stating the required scope (alerts.read where the application is) and by explaining evaluation states (ok, unknown with unknown_reason, not_evaluated before first run). The careful note that covered_by_organisation_rules is null when an environment was not read — "never that nothing watches it" — heads off a serious misreading, though it edges into return-value territory.

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?

Purpose and the own/own=false split are front-loaded and nothing is filler, but it arrives as one dense paragraph mixing scope, return fields, and permission requirements. A little structural separation would improve scanability without lengthening it.

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?

For a two-parameter read tool with no output schema, the description covers what is returned (says, condition, send_to, enabled state, last firing, evaluation) plus auth requirements and the null-vs-false trap. An agent has everything needed to call it and interpret the response correctly.

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 baseline is 3, but the description adds genuine meaning beyond the schema text: environment_id does not just filter, it also triggers listing of organisation rules and populates covered_by_organisation_rules (null when unread). That is semantic content the schema does not carry.

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?

Opens with a specific verb and resource ("List the alerts of one Application") and immediately splits the result space into own alerts (own=true) versus organisation rules (own=false). It names the sibling tools that mutate each class (update_application_alert, delete_application_alert, and the organisation alert tools), so an agent can place it in the toolset without opening another schema.

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?

Gives an explicit conditional: without environment_id only the application's own alerts are relevant, with environment_id the organisation rules watching that environment's clusters are listed beside them. It also routes mutation intents to the correct alternatives and notes which class of alert each alternative governs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.