FlareWarden

• check_service_status — Use this when the user asks whether a third-party service such as Stripe, AWS, GitHub, Slack, OpenAI or Cloudflare is down, slow or having an outage, or why som
• check_service_status_url — Use this when the user asks whether a specific website, URL or API endpoint is down, unreachable or slow: "is my site down or is it just me?", "is api.example.c
• recommend_monitoring — Use this when the user asks what they should monitor for a website, what could take their site down, or which third-party services (hosting, CDN, DNS, payments,
• explain_features — Use this when the user asks what FlareWarden can do or what it costs: "can FlareWarden watch cron jobs?", "how do you confirm an outage?", "what does a status p
• search_help — Use this when the user asks how to do something in FlareWarden, such as adding a custom domain to a status page, sending alerts to Slack, adding a cron job hear
• get_account_overview — Use this when starting any conversation about the user's own FlareWarden account, or when they ask what is wrong, what needs attention, or what they could set u
• get_usage — Use this when the user asks how many monitors they have left, what their plan includes, or why they cannot add more. Returns the monitor pool (used, allowed, le
• list_sites — Use this when the user asks which websites or APIs they monitor, which are down, slow or paused, or what is in a group. Returns each site's status, last check,
• get_site — Use this when the user asks about one of their websites or APIs: is it up, why is it down, what is checked on it, when its certificate or domain expires. Return
• get_monitor_history — Use this when the user asks what a site's recent checks, response times or failures looked like, or how a cron job, content check or dependency has been running
• get_report — Use this when the user wants an uptime, SLA or incident report for a site, a group (an agency's client) or the whole account, for a week, month or quarter. Retu
• list_incidents — Use this when the user asks what went down, whether anything is down now, what happened last night or this month, or what maintenance is planned. Returns incide
• get_incident — Use this when the user asks whether an outage was real, how it was confirmed, when it started and ended, what else it affected, or who was told. Returns the inc
• diagnose_site — Use this when one of the user's own sites is down, failing from some places, slow or alerting, and they want to know why right now, or want it checked from ever
• review_coverage — Use this when the user asks what they are not monitoring, what could break without them knowing, whether their monitoring is complete, or what to set up next. R
• review_noise — Use this when the user asks why a site keeps alerting, which monitors are noisy or flapping, whether alerts were false alarms, or how to get fewer pointless ale
• list_status_pages — Use this when the user asks about their public status pages: which they have, their addresses, how many subscribers, or whether a custom domain works. Returns e
• get_status_page — Use this when the user asks what one of their status pages shows, which sites and checks are on it, or why its custom domain is not working. Returns the page wi
• list_team — Use this when the user asks who has access to the account, what roles people have, who was invited, or how many seats are left. Returns members with role, scope
• search_service_catalog — Use this when the user asks whether FlareWarden can watch a third-party service their site depends on (a payment provider, cloud, CDN, email or auth service). R
• invite_member — Use this when the user wants to give a person access to their FlareWarden account: a teammate at a role (admin, editor or viewer), or a client who should see on
• revoke_invitation — Use this when the user wants to withdraw an invitation that has not been accepted yet. Returns which invitation was cancelled; the link in its email stops worki
• change_member_role — Use this when the user wants a team member to have a different role (admin, editor or viewer) or to cover different monitors. Returns the member's old and new r
• change_member_access — Use this when the user wants a monitor-only member, such as a client, to see more of the account's sites, to view or edit a site they can see, or to stop seeing
• rename_account — Use this when the user wants the FlareWarden account's own name changed: the name its members see in the sidebar and account switcher, and invitations carry. Re
• get_my_notifications — Use this when the user asks which alert emails they get from FlareWarden, or before changing them. Returns their own switches for this account: monitor_down (a
• update_my_notifications — Use this when the user wants FlareWarden to email them more or fewer kinds of alert, pause or resume all alert emails, or change when SSL expiry warnings arrive
• list_webhooks — Use this when the user asks where FlareWarden sends alerts besides email: their webhooks and Slack, Discord, Google Chat or Microsoft Teams channels, which even
• list_webhook_deliveries — Use this when the user asks whether a webhook or chat channel got a particular alert, why one is failing, or what was sent to it lately. Returns its latest deli
• add_webhook — Use this when the user wants FlareWarden to send alert events to their own HTTPS endpoint (a generic, signed JSON webhook), or to connect Slack, Discord, Google
• update_webhook — Use this when the user wants a webhook or chat channel to get different alerts: rename it, change the events or sites it is sent, turn it off or on, or move a c
• test_webhook — Use this when the user wants to check that a webhook or chat channel receives FlareWarden's alerts. Sends one test event to the destination now, records the del
• retry_webhook_delivery — Use this when the user wants a delivery a webhook or chat channel missed sent again, once the endpoint is fixed. Sends the same event again as a new attempt, as
• search_audit_log — Use this when the user asks who changed something in the account and when: who paused a site, who invited someone, what an AI agent did. Returns entries newest
• plan_site — Use this when the user wants FlareWarden to monitor a website or API they run, or up to 50 of them at once. Returns a plan: what each site runs on (hosting, CDN
• create_site — Use this when the user has confirmed a plan_site plan and its cost. Returns what was created for each site (the site, its page checks and dependencies, with ids
• plan_dependency — Use this when the user wants FlareWarden to watch a third-party service a site relies on (a cloud provider, CDN, payment, email or auth service), either while p
• add_dependency — Use this when the user has confirmed a plan_dependency plan for a site already monitored. Returns the dependency created, with its id and how it is watched. Spe
• apply_dependency_change — Use this when the user has confirmed a plan_dependency plan that changes which components of a dependency the site already watches, or how serious each is. Retu
• plan_content_check — Use this when the user wants FlareWarden to watch what a page of their site says or shows: that a text or button is there, an error message is not, a price stay
• add_content_check — Use this when the user has confirmed a plan_content_check plan. Returns the content check created, with its id. Spends one monitor. Safe to repeat: the same pla
• plan_cron_monitor — Use this when the user wants to know if a scheduled job, backup, queue worker or other background task stops running, runs late or fails. Returns the schedule u
• add_cron_monitor — Use this when the user has confirmed a plan_cron_monitor plan. Returns the job's ping URL and ready-to-paste code for crontab, start/complete/fail reporting, Gi
• update_monitor — Use this when the user wants to change how a site or one of its checks is watched: a site's name, interval, timeout or group; a content check's text, selector,
• set_monitor_paused — Use this when the user wants to stop or restart checks of a site or one of its checks, for example during planned work. Returns the new state and what it means:
• plan_bulk_pause — Use this when the user wants to pause or resume several sites at once: a group, a list of sites, or every site, for example during a migration or a move to a ne
• apply_bulk_pause — Use this when the user has confirmed a plan_bulk_pause plan. Returns each site's outcome: paused or resumed, already so, or refused with the website's reason (a
• set_anomaly_detection — Use this when the user wants FlareWarden to alert on unusual response times of a site, or unusual run times of a cron job, or to stop doing so or change how sen
• dismiss_anomaly — Use this when the user says an unusual response or run time was expected (a deploy, a sale, a migration). Returns the anomaly's new state. A dismissed anomaly n
• track_subdomain_certificate — Use this when the user wants FlareWarden to watch the TLS certificate of a subdomain it found under a site (from public certificate logs), or to stop. Returns t
• plan_dns_watch — Use this when the user wants to know if DNS records under one of their sites change or stop resolving: their MX records, _dmarc, SPF, or the CNAME a subdomain p
• add_dns_watch — Use this when the user has confirmed a plan_dns_watch plan. Returns the watch with the values it starts from. It costs no monitors. Safe to repeat: the same pla
• dismiss_suggestion — Use this when the user says not to suggest something again: a status page, an alert channel, inviting a teammate, cron monitoring, subdomains or anomaly detecti
• plan_status_page — Use this when the user wants a public status page for their customers, made from one of their sites or empty. Returns a suggested address (with free alternative
• create_status_page — Use this when the user has confirmed a plan_status_page plan, including publishing it. Returns the new page's public address and what it shows. The page is publ
• update_status_page — Use this when the user wants to change an existing status page's name, description or custom domain, its colours or logo, what it displays (time zone, incident
• add_status_page_component — Use this when the user wants another of their sites, or a group heading, shown on one of their status pages. Returns what was added: a site with the checks chos
• update_status_page_component — Use this when the user wants a service or group on one of their status pages renamed, described differently, moved into or out of a group, or moved up or down.
• remove_status_page_component — Use this when the user wants a site, check or group heading taken off one of their public status pages. A site goes with its own content, dependency and cron ro
• draft_incident_post — Use this when the user wants to tell customers about a problem on one of their sites: declare a new incident, post an update on one, or resolve one. Returns the
• publish_incident_post — Use this when the user has approved a draft_incident_post draft's exact text and recipients. Posts it as the dashboard's Incidents tab does: it shows on the sta
• draft_maintenance — Use this when the user plans work on a site (a deploy, an upgrade, a migration) and wants it marked as maintenance, once or on a schedule, optionally telling st
• schedule_maintenance — Use this when the user has approved a draft_maintenance draft. Schedules it as the dashboard's Maintenance page does: it shows on the status pages, and subscrib
• update_maintenance — Use this when the user wants to change planned or running maintenance: end it early or start it now, extend or move it, rename it, or pause or resume a recurrin
• cancel_maintenance — Use this when the user calls off planned work: a scheduled or running maintenance window, or a recurring schedule as a whole. Cancels it as the dashboard's Main

No hidden text found in the tool definitions.

Text a person reading a tool definition does not see and a model does. Invisible characters can be pasted in by accident; this says what is there, not why. Covers tools only, not prompts or resources.