Skip to main content
Glama
Sign In

Phare

by io.phare.mcp
OverviewDiscussionsAdmin

List alert rules

list_alert_rules
Read-onlyIdempotent

Get a paginated list of the alert rules notifying an integration when an event happens in the project: the project alert rules first, then the organization-wide ones.

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": {
      "project_id": "<project_id>"
    },
    "name": "list_alert_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number to show
per_pageNoNumber of resources to return per page
project_idYesID of the project to act on, see whoami

Output Schema

NameRequiredDescriptionDefault
dataNo
metaNoMeta data for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "items": {
+        "properties": {
+          "created_at": {
+            "description": "Date of creation for the entity",
+            "format": "date-time",
+            "type": "string"
+          },
+          "event": {
+            "description": "Name of the event that will trigger the execution of the alert rule",
+            "enum": [
+              "uptime.monitor.created",
+              "uptime.monitor.deleted",
+              "uptime.monitor_certificate.discovered",
+              "uptime.monitor_certificate.expiring",
+              "uptime.incident.created",
+              "uptime.incident.propagated",
+              "uptime.incident.partially_recovered",
+              "uptime.incident.recovered",
+              "uptime.incident_comment.created",
+              "uptime.incident_update.published",
+              "uptime.maintenance_window.in_progress",
+              "uptime.maintenance_window.completed",
+              "uptime.maintenance_window.cancelled"
+            ],
+            "type": "string"
+          },
+          "event_settings": {
+            "anyOf": [
+              {
+                "title": "Empty",
+                "type": [
+                  "object",
+                  "null"
+                ]
+              },
+              {
+                "properties": {
+                  "type": {
+                    "description": "Type of incident to notify about",
+                    "enum": [
+                      "all",
+                      "monitor",
+                      "manual"
+                    ],
+                    "examples": [
+                      "all"
+                    ],
+                    "type": "string"
+                  }
+                },
+                "title": "Uptime incident",
+                "type": "object"
+              },
+              {
+                "properties": {
+                  "days_before_expiry": {
+                    "description": "Days to notify before the certificate expires",
+                    "examples": [
+                      25
+                    ],
+                    "type": "integer"
+                  }
+                },
+                "title": "Uptime certificate expiring",
+                "type": "object"
+              }
+            ],
+            "description": "Additional settings for the event"
+          },
+          "id": {
+            "examples": [
+              1
+            ],
+            "type": "integer"
+          },
+          "integration_id": {
+            "description": "The ID of the integration used to send a notification when the alert rule is executed",
+            "examples": [
+              1
+            ],
+            "type": "integer"
+          },
+          "integration_settings": {
+            "anyOf": [
+              {
+                "title": "Empty",
+                "type": [
+                  "object",
+                  "null"
+                ]
+              },
+              {
+                "properties": {
+                  "priority": {
+                    "description": "Notification priority level",
+                    "enum": [
+                      "min",
+                      "low",
+                      "default",
+                      "high",
+                      "max"
+                    ],
+                    "examples": [
+                      "default"
+                    ],
+                    "type": "string"
+                  }
+                },
+                "title": "Ntfy",
+                "type": "object"
+              },
+              {
+                "properties": {
+                  "schema": {
+                    "description": "JSON schema defining the webhook payload structure",
+                    "examples": [
+                      "{\"id\": \"{{ alert_rule_request.id }}\", \"event\": \"{{ event.key }}\"}"
+                    ],
+                    "format": "json",
+                    "type": "string"
+                  }
+                },
+                "title": "Outgoing Webhooks",
+                "type": "object"
+              },
+              {
+                "properties": {
+                  "expire": {
+                    "description": "Seconds after which an unacknowledged `emergency` priority notification stops repeating. Required by the `emergency` priority, unused by the others.",
+                    "examples": [
+                      3600
+                    ],
+                    "type": [
+                      "integer",
+                      "null"
+                    ]
+                  },
+                  "priority": {
+                    "description": "Notification priority level",
+                    "enum": [
+                      "lowest",
+                      "low",
+                      "normal",
+                      "high",
+                      "emergency"
+                    ],
+                    "examples": [
+                      "normal"
+                    ],
+                    "type": "string"
+                  },
+                  "retry": {
+                    "description": "Seconds between the repeats of an `emergency` priority notification until it is acknowledged. Required by the `emergency` priority, unused by the others.",
+                    "examples": [
+                      300
+                    ],
+                    "type": [
+                      "integer",
+                      "null"
+                    ]
+                  }
+                },
+                "title": "Pushover",
+                "type": "object"
+              }
+            ],
+            "description": "Additional settings for the integration"
+          },
+          "project_id": {
+            "description": "The ID of a project to use as a scope",
+            "examples": [
+              1
+            ],
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "rate_limit": {
+            "description": "Minimum time in minutes between two executions of the alert rule, used to minimize the number of alerts received.",
+            "enum": [
+              0,
+              5,
+              10,
+              30,
+              60,
+              180,
+              720,
+              1440
+            ],
+            "examples": [
+              5
+            ],
+            "type": "integer"
+          },
+          "updated_at": {
+            "description": "Date of last update for the entity",
+            "format": "date-time",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "meta": {
+      "description": "Meta data for pagination",
+      "properties": {
+        "current_page": {
+          "examples": [
+            2
+          ],
+          "type": "integer"
+        },
+        "from": {
+          "examples": [
+            11
+          ],
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "has_more_pages": {
+          "description": "Whether a next page exists, fetched with the page argument",
+          "type": "boolean"
+        },
+        "per_page": {
+          "examples": [
+            100
+          ],
+          "type": "integer"
+        },
+        "to": {
+          "examples": [
+            20
+          ],
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare this as a read-only, idempotent, non-destructive operation. The description adds useful behavioral detail beyond that: results are paginated, project-level rules are returned before organization-wide rules, and the list is tied to alert rules that notify an integration. It does not discuss permissions or rate limits, but the added ordering and scope context are valuable.

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 a single well-formed sentence with no filler. It front-loads the core action and then adds the most important scoping and ordering detail, making efficient use of space.

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 paginated read/list tool, the description covers the essential context: what is listed, which project scope is used, and the ordering of project versus organization-wide rules. With rich annotations, a complete input schema, and an output schema, no critical invocation detail is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents project_id, page, and per_page. The description reinforces that project_id scopes the result to a project and also includes organization-wide rules, but it does not add syntax or format details beyond the schema. A baseline score of 3 is appropriate.

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 and resource: 'Get a paginated list of the alert rules.' It also defines the scope clearly by specifying rules that notify an integration when an event happens, and it distinguishes the result set from a single-rule fetch by saying it returns project rules first and then organization-wide ones.

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 gives clear context for when to use this tool: listing alert rules associated with a project and its organization. It does not explicitly mention alternatives such as get_alert_rule for a single rule, so it lacks exclusion guidance, but the usage context is unambiguous.

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

All Phare toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources