Skip to main content
Glama
jakedx6

Helios-9 MCP Server

by jakedx6

list_workflow_rules

List automation rules for a project or across the entire workspace. Filter by project ID or enabled status to view specific rules.

Instructions

List all automation rules for a project or globally

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoProject ID to filter rules (optional)
enabled_onlyNoOnly return enabled rules

Implementation Reference

  • The main handler function for the 'list_workflow_rules' tool. Calls supabaseService.getWorkflowRules() with optional project_id and enabled_only filters, then returns the rules along with counts.
    export const listWorkflowRules = requireAuth(async (args: any) => {
      const { project_id, enabled_only } = ListWorkflowRulesSchema.parse(args)
      
      logger.info('Listing workflow rules', { project_id, enabled_only })
    
      const rules = await supabaseService.getWorkflowRules({
        project_id,
        enabled: enabled_only ? true : undefined
      })
    
      return {
        rules,
        total_rules: rules.length,
        active_rules: rules.filter(r => r.enabled).length
      }
    })
  • Input validation schema (Zod) for list_workflow_rules. Defines optional project_id string and enabled_only boolean (default true).
    const ListWorkflowRulesSchema = z.object({
      project_id: z.string().optional(),
      enabled_only: z.boolean().default(true)
    })
  • Tool registration object (MCPTool) for 'list_workflow_rules'. Defines name, description, and inputSchema for the MCP tool listing.
    export const listWorkflowRulesTool: MCPTool = {
      name: 'list_workflow_rules',
      description: 'List all automation rules for a project or globally',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: {
            type: 'string',
            description: 'Project ID to filter rules (optional)'
          },
          enabled_only: {
            type: 'boolean',
            default: true,
            description: 'Only return enabled rules'
          }
        }
      }
    }
  • Export of all workflow automation handlers, mapping 'list_workflow_rules' to the listWorkflowRules handler function.
    export const workflowAutomationHandlers = {
      create_workflow_rule: createWorkflowRule,
      list_workflow_rules: listWorkflowRules,
      execute_workflow_rule: executeWorkflowRule,
      create_trigger_automation: createTriggerAutomation,
      get_automation_analytics: getAutomationAnalytics
    }
  • Backend API helper getWorkflowRules() called by the handler. Currently a placeholder returning empty array (not yet implemented in API).
    async getWorkflowRules(filter: any): Promise<any[]> {
      logger.warn('Workflow rules not yet implemented in API')
      return []
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, and the description does not disclose behavioral traits such as read-only nature, pagination, or rate limits. The term 'List' weakly implies read-only, but additional detail is missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded, no redundant information. Every word is necessary and clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and no annotations, the description is minimally adequate for a simple listing tool. Missing details on return format, sorting, or behavior with no rules.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with parameter descriptions. The description adds context about global vs project scoping, but does not provide further meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List'), resource ('automation rules'), and scope ('for a project or globally'), distinguishing it from sibling tools like create_workflow_rule or execute_workflow_rule.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by stating scoping (project or global), but lacks explicit guidance on when to use this tool vs alternatives like create_trigger_automation or search_workspace.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jakedx6/helios9-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server