| name | formae-status |
| description | Use when the user asks about running commands, deployment progress, recent operations, command history, or what failed |
Command Status and Monitoring
Use list_commands and get_command_status MCP tools to monitor formae operations.
Targeting an environment (profile)
list_commands and get_command_status hit the formae agent's API directly and take an optional profile argument. If the user is working against a specific environment (e.g. prod, staging), pass that profile name as profile on each call in this flow so it targets that environment — for this session only, without changing global state. If which environment they mean is unclear and list_profiles shows more than one, ask first. Never use use_profile to "set up" this session — the active profile is global and shared with the user's CLI and any other open sessions. When no profile is named, the active profile is used. Requires formae >= 0.87.0.
Workflow
- For an overview: call
list_commands (optionally with a query)
- For a specific command: call
get_command_status with the command ID
- Present status clearly with resource update progress
Common Queries
| User asks... | Tool + Query |
|---|
| "What's running?" | list_commands with status:in_progress |
| "Show recent commands" | list_commands (no query, defaults to 10 most recent) |
| "What failed?" | list_commands with status:failed |
| "Show my commands" | list_commands with client:me |
| "Status of cmd-123" | get_command_status with command_id: cmd-123 |
Watching a Command
When the user asks to "watch" or "follow" a command:
- Call
get_command_status with the command ID
- If the command is still
in_progress, report current progress
- Offer to check again after a short interval
- Continue until the command reaches a terminal state (
completed, failed, canceled)
Command States
- pending: Queued, not yet started
- in_progress: Currently executing
- completed: Successfully finished
- failed: Encountered errors
- canceled: Stopped by user
