Choose an incident to inspect or provide the facts for a new one. AI can summarize customer impact and create an incident with your supplied details.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Find an incident and read its details for a focused incident summary.
/oo FireHydrant: Find FireHydrant incidents matching [service, status, or date filters]. Read incident [incident ID] and summarize its status, customer impact, and available response context.
Prepare a concise incident name and impact summary and create the incident.
/oo FireHydrant: Create a FireHydrant incident named [name] using these facts [facts]. Set severity [severity] and customer impact [impact], with affected services and environments [impact references].
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect a FireHydrant API key.
Connect FireHydrant →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
FireHydrant incident records describe response context and impact. Service and environment catalog reads help identify resources associated with an incident.
Find incidents with status, service, environment, or date filters; inspect one or create a new incident.
List or retrieve service and environment records to identify affected resources.
List FireHydrant incidents with stable pagination and common filters.
Leina 
Wanta 
firehydrant.list_incidents Retrieve a single FireHydrant incident by ID.
firehydrant.get_incident Create a FireHydrant incident using a JSON-friendly request body.
firehydrant.create_incident List FireHydrant services with pagination and search filters.
firehydrant.list_services Retrieve a single FireHydrant service by UUID or slug.
firehydrant.get_service List FireHydrant environments with pagination and search filters.
firehydrant.list_environments Retrieve a single FireHydrant environment by UUID or slug.
firehydrant.get_environment No matching tools.
Yes. Filter incidents by services and optionally their status, environment, or creation dates.
Supply a name and verified details such as the summary, customer impact, severity, and affected resources.
These operations read incidents and create new ones. Existing incident updates and resolution are not included.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.