ππ’πΉπΈβππΉπππΉπ’π - Intelligent Guidance for
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_workflow_reportB | Generates interactive workflow reports and analytics dashboards with rich visualizations and real-time data tracking. |
| get_report_statusC | Retrieves current status and results of a report generation request. |
| get_workflow_guidanceC | Provides minimal role identity and basic capabilities for workflow execution. |
| get_step_guidanceC | Provides focused guidance for executing the current workflow step, including commands and validation checklist. |
| report_step_completionC | Report step completion results and get next step guidance. |
| get_step_progressC | Get focused step progress summary for a task. |
| get_next_available_stepC | Get focused next step information for role progression. |
| get_role_transitionsC | Gets available role transitions with recommendations, scores, and basic requirements for workflow progression. |
| validate_transitionC | Validates role transition requirements and provides pass/fail status with actionable feedback. |
| execute_transitionC | Executes role transition and returns execution status with essential details for next steps. |
| get_transition_historyB | Retrieves transition history with timeline overview and basic statistics for task context. |
| workflow_execution_operationsC | Manages workflow execution state through strongly-typed operations for creating, querying, updating, and completing workflow executions. Handles execution context and progress tracking with validated parameters. |
| bootstrap_workflowC | Initializes a new workflow execution with boomerang role, starting from git setup through task creation and delegation. |
| get_operation_schemaA | Get the parameter schema definition for a specific MCP service and operation. Returns the exact structure needed for parameters when calling execute_mcp_operation. Useful for understanding what parameters are required and optional for any service operation. |
| execute_mcp_operationC | Core workflow operations service for executing database and business logic operations through MCP services like TaskOperations, PlanningOperations, WorkflowOperations, etc. Uses consistent parameters and follows strict naming conventions. |
| init_rulesC | Initialize Anubis workflow rules to specified AI agent (cursor or copilot) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
The tool set has clear thematic grouping around workflow execution, transitions, and guidance, but there is significant overlap in purpose. For example, get_step_guidance, get_workflow_guidance, and get_next_available_step all provide guidance-related information, which could confuse an agent about which to use. Similarly, execute_mcp_operation and workflow_execution_operations both handle workflow operations, though their descriptions hint at different scopes.
Most tools follow a consistent verb_noun pattern (e.g., execute_mcp_operation, generate_workflow_report, get_role_transitions), which aids readability. However, there are minor deviations such as init_rules (verb_noun but abbreviated) and workflow_execution_operations (noun-heavy, less action-oriented), slightly disrupting the pattern.
With 16 tools, the count is borderline for a workflow guidance server. It feels heavy due to overlapping tools, but it might be justified if each serves a distinct niche in a complex domain. The scope appears broad, covering initialization, execution, transitions, reporting, and guidance, which could warrant this number, but it risks being overwhelming.
The tool surface covers key aspects of workflow management: initialization (bootstrap_workflow, init_rules), execution (execute_mcp_operation, workflow_execution_operations), transitions (execute_transition, validate_transition), guidance (get_step_guidance, get_workflow_guidance), and reporting (generate_workflow_report, get_report_status). Minor gaps might exist, such as tools for deleting or archiving workflows, but core workflows are well-supported.