Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

list_workflow_rules

Retrieve available workflow rules with input/output specifications for data processing, validation, or business logic in compliance workflows.

Instructions

Retrieve available workflow rules.

Rules are predefined logic that can be executed in workflow nodes. They typically handle data processing, validation, or business logic. Rules have inputs and outputs that can be mapped to other workflow components.

Returns: - rules (List[WorkflowRuleVO]): List of available workflow rules with input/output specifications - id (str) - name: (str) - description (str) - ruleInputs: [List[WorkflowRuleInputsVO]] - ruleOutputs: [List[WorkflowRuleOutputsVO]]

- error (Optional[str]): An error message if any issues occurred during retrieval. 

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
rulesNo
errorNo

Implementation Reference

  • Constants used by list_workflow_rules: URL_WORKFLOW_PREBUILD_RULES = '/v1/rules' is the API endpoint called by the handler to fetch workflow prebuilt rules.
    URL_WORKFLOW_PREBUILD_TASKS = "/v1/workflow-catalog/tasks"
    URL_WORKFLOW_PREBUILD_RULES = "/v1/rules"
    URL_WORKFLOW_PREDEFINED_VARIABLES = "/v1/workflow-catalog/predefined-variables"
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format and error field, confirming it's a read operation. However, it lacks details on authentication, rate limits, or side effects, which is acceptable for a simple list tool.

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

Conciseness3/5

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

The description includes a definition of workflow rules that might be redundant for an AI agent familiar with the domain. The return spec is formatted as a list, which is clear but somewhat verbose. Could be more concise.

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

Completeness4/5

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

Given the absence of parameters and annotations, the description is fairly complete. It explains the tool's purpose and return structure. However, it doesn't mention pagination or filtering possibilities, which are not needed here. Minor gap.

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

Parameters4/5

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

The tool has zero parameters, so the baseline is 4. The schema coverage is 100% (empty schema), and the description adds no parameter details because none exist.

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 starts with 'Retrieve available workflow rules,' clearly stating the verb and resource. It distinguishes from sibling tools like fetch_workflow_rule by being a list operation, and provides context on what workflow rules are.

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

Usage Guidelines2/5

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

The description does not specify when to use this tool versus alternatives like fetch_workflow_rule or fetch_rule. No guidance on when not to use it or prerequisites, leaving the agent to infer usage from context.

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/ComplianceCow/cow-mcp'

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