Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

create_workflow

Create compliance workflows from YAML to establish workflow IDs, automate governance processes, and generate visual audit diagrams.

Instructions

Create a new workflow using YAML definition. Always display the workflow diagram. Before creation confirm workflow name and creation with the user before executing this tool. Later use 'modify_workflow' tool to update states, activities, conditions, and transitions.

yaml struct:

metadata: name: description: summary: mermaidDiagram:

This function creates a workflow from a YAML specification.

Create workflow (establishes the ID) Update summary (document what we're building) Update mermaid diagram (visualize the flow) Then modify workflow (implement the actual logic)

Args: workflow_yaml: YAML string defining the workflow structure

Returns: Success message with workflow ID or error message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_yamlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Displays confirmation requirement, diagram display mandate, and documents the multi-step creation sequence (create → update → modify) without annotations to contradict.

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?

Contains redundancy between opening sentence and 'This function creates...', and the process list repeats earlier guidance about modify_workflow.

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?

Adequately covers the complex multi-tool workflow pattern and return value despite presence of output schema.

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?

Compensates for 0% schema coverage by providing YAML structure example (metadata fields) and basic parameter description.

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?

States specific action (create workflow from YAML) and explicitly distinguishes from sibling 'modify_workflow' for updates.

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

Usage Guidelines5/5

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

Explicitly requires user confirmation before execution and clearly indicates when to use 'modify_workflow' instead for updates.

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