Leina 
Wanta 
Review account usage
Read billing metrics and daily usage with explicit period and timezone.
/oo OOMOL Console: Read OOMOL billing summary and usage breakdown for [days] days with UTC offset [offset], then explain major usage sources.
Connect OOMOL Console to Your AI Agent
Ask your AI assistant to work with OOMOL Console: review Team Connections and Account Usage.
15 tools No auth
Try a OOMOL Console Task
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
oo Skill OOMOL Console
Audit connection permissions
Read team connections and a selected connection's permission groups.
/oo OOMOL Console: List current-team OOMOL Connections, then read permission groups for Connection app ID [app ID] and summarize assignments.
Start Working with OOMOL Console
-
Install OOMOL
Set up oo CLI and the oo Skill in your agent.
Install OOMOL → -
Connect OOMOL Console
Use your authenticated OOMOL account and current team scope.
Connect OOMOL Console → -
Give Your Agent a Task
Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →
Choose Your Agent
- An authenticated OOMOL account or service account with access to the current team.
OOMOL Console Tools
OOMOL Console actions use the current authenticated principal and team scope to expose billing, members, Connections, and permission groups.
Review account usage
Read billing metrics and daily usage with explicit period and timezone.
Audit connection permissions
Read team connections and a selected connection's permission groups.
15 tools
Get Current Scope
Return the current OOMOL team scope and authenticated principal.
oomol_console.get_current_scope List Teams
List the OOMOL teams visible to the authenticated account.
oomol_console.list_teams Get Team Summary
Return metadata and member counts for the current OOMOL team.
oomol_console.get_team_summary Get Balance
Return every available balance lot for the authenticated OOMOL account.
oomol_console.get_balance Get Billing Summary
Return the compact OOMOL account billing metrics shown by Console.
oomol_console.get_billing_summary Get Usage Breakdown
Return the daily OOMOL account usage breakdown by source and subject.
oomol_console.get_usage_breakdown List Members
List members of the current OOMOL team.
oomol_console.list_members List Team Connections
List the current-team Connections visible to the authenticated user or service account.
oomol_console.list_team_connections List Connection Permission Groups
List the default and custom permission groups for one current-team Connection.
oomol_console.list_connection_permission_groups Update Connection Default Permission Group
Replace the action permission of a Connection's non-deletable default permission group.
oomol_console.update_connection_default_permission_group Create Connection Permission Group
Create a custom Connection permission group and replace the assignments of its members.
oomol_console.create_connection_permission_group Update Connection Permission Group
Replace the name, member assignments, and action permission of a custom Connection permission group.
oomol_console.update_connection_permission_group Delete Connection Permission Group
Delete a custom Connection permission group so its members return to the default group.
oomol_console.delete_connection_permission_group Add Member
Add an OOMOL user to the current team with the member role.
oomol_console.add_member List Connection Executions
List the execution records shown on an OOMOL Console Connection details page.
oomol_console.list_connection_executions No matching tools.
Frequently Asked Questions
Does no_auth mean public access?
No separate provider credential is needed, but actions use the authenticated OOMOL principal and its allowed team scope.
Why do permission changes need a revision?
Permission-group mutations require the current revision so changes can be checked against the connection's current configuration.
Can I inspect execution records?
list_connection_executions retrieves Console-visible execution records using appId and limit.