Skip to main content
Glama
Sign In

Phare

by io.phare.mcp
OverviewDiscussionsAdmin

Get an alert rule

get_alert_rule
Read-onlyIdempotent

Get an alert rule by ID, with its event, integration, rate limit and settings.

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>",
      "alert_rule_id": "<alert_rule_id>"
    },
    "name": "get_alert_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesID of the project to act on, see whoami
alert_rule_idYesID of the alert rule to show

Output Schema

NameRequiredDescriptionDefault
idNo
eventNoName of the event that will trigger the execution of the alert rule
created_atNoDate of creation for the entity
project_idNoThe ID of a project to use as a scope
rate_limitNoMinimum time in minutes between two executions of the alert rule, used to minimize the number of alerts received.
updated_atNoDate of last update for the entity
event_settingsNoAdditional settings for the event
integration_idNoThe ID of the integration used to send a notification when the alert rule is executed
integration_settingsNoAdditional settings for the integration

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "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"
+}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds the fact that related data (event, integration, rate limit, settings) is inlined in the response, which is genuinely useful beyond the annotations, but nothing is said about error behavior when the ID is missing.

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?

A single front-loaded sentence with no filler; the returned-resource list is slightly dense but every clause carries information. Nothing is redundant with the title.

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?

For a simple two-parameter read tool with full schema coverage, complete annotations and an output schema, the description covers identity and response composition. The only minor gap is routing guidance relative to list_alert_rules.

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% and both required parameters are documented in the schema, including the pointer to whoami for project_id. The description adds no meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Get an alert rule by ID') and adds what comes back ('event, integration, rate limit and settings'), which clearly separates it from list_alert_rules. It is clear but does not explicitly mention the sibling it contrasts with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus list_alert_rules or get_monitor; 'by ID' implies single-item retrieval but no condition or alternative is stated. The agent must infer the choice from the tool name alone.

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