Skip to content
Glowo
Esc
↑↓navigate↵open⌘Jpreview
On this page

Tools

Every tool Glowo's MCP server gives an agent, what it does, and the access it needs.

These are the tools Glowo’s MCP server at https://api.glowo.dev/mcp offers. Your client shows the agent each tool’s parameters, so this page says what each one does and what it needs.

  • Needs is the scopes a call must carry. A write or delete scope also covers the matching read.
  • Lowest level is the narrowest access level on the consent screen that grants them.
  • An API key needs the same capabilities, and must allow MCP.

Every connection sees every tool. Calling one it was not granted returns an error naming the missing scope, and the agent is told to say so rather than work around it.

The tools

Workspace

ToolWhat it doesNeedsLowest level
glowo_whoamiSay which workspace this connection acts in, what it may do (an OAuth connection's scopes, or an API key's capabilities) and on whose behalf. Call it first.NothingRead Only

Monitors

ToolWhat it doesNeedsLowest level
glowo_list_monitorsList monitors in the workspace. Returns a slim payload (no dailyStats / heartbeats / flapState / config) — use glowo_get_monitor for full details. A non-null checkInterruption means the status shown is the last confirmed one and checks are interrupted or outage confirmation is paused. Supports limit/offset pagination.monitors:readRead Only
glowo_get_monitorGet full details for a single monitor (config, current status, last heartbeat). A non-null checkInterruption means the status shown is the last confirmed one and checks are interrupted or outage confirmation is paused.monitors:readRead Only
glowo_get_monitor_statsWorkspace-wide monitor statistics: counts by status, uptime trends, recent incidents.monitors:readRead Only
glowo_get_monitor_hourly_statsA monitor's uptime hour by hour over a period: up, down and degraded counts and average latency for each hour, across every region or only the ones named.monitors:readRead Only
glowo_list_heartbeatsA monitor's heartbeats (check results), newest first: status, latency, status code, region and message, over a period or for some regions if asked. Use it to spot flapping or recent failures, then call glowo_get_heartbeat_detail with a heartbeat's id for its timings, response and assertion results.monitors:readRead Only
glowo_get_heartbeat_detailFull per-check detail for a single heartbeat: timings, response headers/body, assertion results, resolved IP. Use to triage a DOWN check.monitors:readRead Only
glowo_create_monitorCreate a new monitor. Tip: run glowo_probe_url first to validate the target before creating. Optional projectIds attaches the new monitor to one or more projects.monitors:writeOperate
glowo_update_monitorUpdate fields on an existing monitor (partial — only provided fields change).monitors:writeOperate
glowo_delete_monitorPermanently delete a monitor and all its heartbeats. Cannot be undone.monitors:deleteFull Access
glowo_pause_monitorPause a monitor — suppress checks and alerts until resumed. For planned work, schedule glowo_create_maintenance_window instead: it ends on its own.monitors:writeOperate
glowo_resume_monitorResume a paused monitor — checks and alerts re-enable immediately.monitors:writeOperate
glowo_run_check_nowDispatch an on-demand check across the monitor's regions. Returns `{correlationId}` immediately — the actual heartbeat appears via the normal check pipeline. Poll glowo_list_heartbeats (most recent first) shortly after to find the matching result; typical end-to-end latency is 2–10s depending on region count and TLS handshake time.monitors:writeOperate
glowo_acknowledge_monitorAcknowledge a monitor's alert while it is DOWN or DEGRADED: for the next 30 minutes no new alert for it is sent. Its recovery still is, and its checks keep running. Say in the message what is being done.monitors:writeOperate
glowo_probe_urlSend one request to a URL from Glowo's servers (not from the check regions), without creating a monitor, and read the status code, headers, the start of the body, latency and how any assertions fared. Redirects are not followed. Use it to try a target and its assertions before glowo_create_monitor.monitors:writeOperate
glowo_acknowledge_dns_changeAccept a DNS_DIFF monitor's current records as the intended ones: they become its baseline (with the records its recent checks saw) and the monitor reads UP again.monitors:writeOperate
glowo_list_monitor_acknowledgmentsWho acknowledged a monitor's most recent alerts, when, and the message they left, newest first.monitors:readRead Only
glowo_get_monitor_reportA monitor's SLA report for a period (from before to, ISO 8601): uptime percentage, incident count, average latency, time paused, maintenance time left out of uptime and daily stats.monitors:readRead Only

Projects

ToolWhat it doesNeedsLowest level
glowo_list_projectsList all projects in the workspace.monitors:readRead Only
glowo_create_projectCreate a new project to organize monitors. Slug must be URL-safe and unique within the workspace.monitors:writeOperate
glowo_add_project_monitorsAttach existing monitors to a project. Idempotent — already-attached monitors are skipped.monitors:writeOperate
glowo_remove_project_monitorDetach a monitor from a project. The monitor itself is not deleted — only the membership is removed.monitors:writeOperate
glowo_delete_projectPermanently delete a project and every sub-project under it, with their memberships. Monitors and status pages are not deleted — they only stop belonging to those projects.monitors:writeOperate
glowo_get_projectFetch one project with its monitor and status page counts.monitors:readRead Only
glowo_update_projectRename a project, change its slug or description, or move it under another project (only the fields you send change).monitors:writeOperate

Incidents

ToolWhat it doesNeedsLowest level
glowo_list_incidentsList incidents in the workspace (open and recently resolved).incidents:readRead Only
glowo_get_incidentGet full details for an incident: status, affected components, timeline of updates.incidents:readRead Only
glowo_create_incidentOpen an incident on a status page, to tell its readers about an issue yourself (monitors open their own incidents separately). Get the statusPageId from glowo_list_status_pages. Start with status=INVESTIGATING, then post updates as the situation evolves.incidents:writeOperate
glowo_add_incident_updatePost a timeline update on an existing incident: new message + status. Subscribers are notified per the channel's settings.incidents:writeOperate
glowo_resolve_incidentResolve an incident, with an optional closing note (subscribers receive a resolution notification). With mode undo, takes back a reopening posted by mistake instead.incidents:writeOperate
glowo_reopen_incidentReopen a resolved incident, e.g. when the issue recurs. With mode undo, takes back a resolution posted by mistake instead.incidents:writeOperate
glowo_archive_incidentArchive an incident — hides it from the status page timeline. Required step before glowo_delete_incident. Reversible until deletion. An incident the platform opened for a monitor (autoGenerated) must be resolved first, with glowo_resolve_incident: while open it is tracking a monitor that is still down.incidents:writeOperate
glowo_list_status_page_incidentsList one status page's incidents, newest first. Archived incidents are left out; glowo_list_incidents searches the whole workspace.incidents:readRead Only
glowo_update_incidentCorrect an incident's title, severity or affected components (only the fields you send change). On a published incident the change is public at once.incidents:writeOperate
glowo_edit_incident_updateReword an update already posted on an incident; find its updateId with glowo_get_incident. On a published incident the new wording is public at once.incidents:writeOperate
glowo_publish_incidentPublish a DRAFT or SCHEDULED incident now: it appears on its status page and the page's subscribers are notified.incidents:writeOperate
glowo_schedule_incidentSchedule a DRAFT incident to publish itself at scheduledFor (ISO 8601, in the future), typically announced maintenance.incidents:writeOperate
glowo_unarchive_incidentRestore an archived incident to its status page's incident list.incidents:writeOperate
glowo_delete_incidentPermanently delete an incident (and all its updates). The incident must be archived first via glowo_archive_incident. Use sparingly — for retracting an incident posted by mistake. Prefer glowo_resolve_incident when an incident actually happened.incidents:deleteFull Access

Status pages

ToolWhat it doesNeedsLowest level
glowo_list_status_pagesList status pages in the workspace. Required to discover the statusPageId you need for glowo_create_incident.status_pages:readRead Only
glowo_get_status_pageFetch a single status page by id, including its components, theme, custom domain, and visibility settings.status_pages:readRead Only
glowo_create_status_pageCreate a status page. Like one created in the dashboard, it is public at its address at once; pass visibility UNPUBLISHED to keep it private until glowo_publish_status_page. monitors lists the monitors it shows, by UUID. A customDomain serves the page only once its DNS is verified, from the dashboard.status_pages:writeFull Access
glowo_update_status_pageChange a status page (partial: only the fields you send change). On a published page the change is public at once, including which monitors it shows.status_pages:writeFull Access
glowo_publish_status_pageMake a status page public at its address, for anyone to read.status_pages:writeFull Access
glowo_unpublish_status_pageTake a status page offline: it serves nothing until it is published again. Its incidents and subscribers are kept.status_pages:writeFull Access
glowo_delete_status_pagePermanently delete a status page, with its incidents, postmortems and subscribers. Cannot be undone.status_pages:deleteFull Access

Postmortems

ToolWhat it doesNeedsLowest level
glowo_list_postmortemsList postmortems, newest first, filtered by status page, incident, status (DRAFT or PUBLISHED) or text. Archived ones are listed only with archived: true. Supports limit/offset; returns the total.postmortems:readRead Only
glowo_get_postmortemFetch one postmortem: its status page, incident, status and body or external link.postmortems:readRead Only
glowo_create_postmortemWrite a postmortem for a status page, as a DRAFT nobody else sees until glowo_publish_postmortem. kind INLINE carries a markdown body; kind EXTERNAL links to an http(s) page instead. An incidentId must be a resolved incident on the same page.postmortems:writeOperate
glowo_update_postmortemEdit a postmortem's title, slug, body or external link (only the fields you send change). On a published postmortem the edit is public at once.postmortems:writeOperate
glowo_publish_postmortemPublish a postmortem on its status page, for anyone to read.postmortems:writeOperate
glowo_unpublish_postmortemTake a published postmortem off its status page; it becomes a draft again.postmortems:writeOperate
glowo_archive_postmortemArchive a postmortem: it leaves the status page and default lists, and is kept (list it with archived: true).postmortems:writeOperate
glowo_link_postmortemAttach a postmortem to a resolved incident on the same status page. An incident carries one postmortem at most.postmortems:writeOperate
glowo_unlink_postmortemDetach a postmortem from its incident; the postmortem is kept.postmortems:writeOperate
glowo_delete_postmortemPermanently delete a postmortem. Cannot be undone; archiving keeps it instead.postmortems:deleteFull Access

Maintenance

ToolWhat it doesNeedsLowest level
glowo_list_maintenance_windowsList maintenance windows scheduled for a monitor (past, current, and future).monitors:readRead Only
glowo_create_maintenance_windowSchedule a maintenance window for a monitor. Alerts are suppressed during the window and the public status page shows a maintenance banner.maintenance:writeOperate
glowo_delete_maintenance_windowCancel a scheduled maintenance window. Alerts resume immediately if the window was active.maintenance:writeOperate
glowo_update_maintenance_windowMove or edit a scheduled maintenance window: its title, description, start, end, timezone, recurrence or whether it counts against uptime (only the fields you send change).maintenance:writeOperate

Notifications

ToolWhat it doesNeedsLowest level
glowo_list_notification_channelsList all notification channels (Slack, email, webhooks, etc.) in the workspace.notifications:readOperate
glowo_create_notification_channelCreate a notification channel (email, SMS, Slack, Discord, Telegram, PagerDuty, webhook). `config.type` picks the kind; each kind's fields are in this tool's input schema.notifications:writeOperate
glowo_update_notification_channelUpdate a notification channel — rename, swap config, change events, retarget monitors/projects. Partial: only set the keys you want to change.notifications:writeOperate
glowo_enable_notification_channelEnable a notification channel so it starts firing on its configured events.notifications:writeOperate
glowo_disable_notification_channelDisable a notification channel without deleting it — useful for muting alerts during a known issue or maintenance.notifications:writeOperate
glowo_test_notification_channelSend a test notification through a channel to verify routing/credentials. The message is real: it reaches the channel's destination.notifications:writeOperate
glowo_delete_notification_channelPermanently delete a notification channel and detach it from any monitors that referenced it.notifications:deleteFull Access
glowo_get_notification_channelFetch one notification channel: its type, events, linked monitors and settings, with secrets masked.notifications:readOperate
glowo_list_channel_deliveriesA channel's recent deliveries, newest first: what was sent, whether it arrived, attempts and the last error. Destinations and signed links are masked.notifications:readOperate

Choosing a level

Read Only answers what is up, what is down and why, which is most of what people ask an agent. Operate adds the day-to-day on-call work: creating and changing monitors, running checks, acknowledging alerts, opening, updating and resolving incidents, writing and publishing postmortems, scheduling maintenance and managing notification channels. It cannot set up or change a status page, and cannot delete anything. Full Access adds both.

Was this page helpful?