Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

modify_workflow

Update an existing compliance workflow by providing a new YAML definition that specifies states, activities, conditions, and transitions. Requires the workflow ID.

Instructions

Modify an existing workflow using YAML definition.

The workflow ID (UUID) is required to identify which workflow to modify. This function updates an existing workflow with a new YAML specification. The YAML should define the workflow structure including states, activities, conditions, and transitions. Always display the workflow diagram and confirm with the user before executing this tool.

BEFORE using 'modify_workflow' tool, you MUST check:

  • Do I have the complete CCow workflow YAML schema?

  • Do I know the exact state configuration requirements?

  • Do I understand the data flow and variable reference patterns? If the answer to ANY of these is "no", respond with: "I need CCow workflow schema knowledge to properly implement this workflow. Please provide the workflow YAML specification, state definitions, and integration patterns before I proceed with modify_workflow."

Args: workflow_yaml: YAML string defining the updated workflow structure workflow_id: ID of the workflow to modify

Returns: Success message or error message

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflow_yamlYes
workflow_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Without annotations, the description carries full burden. It discloses the requirement to confirm with user and display diagram, but does not cover side effects, permissions, or locking. The behavioral detail is minimal but present.

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 is front-loaded with the main purpose, but then includes a lengthy checklist and fallback response script which could be more concise. It sacrifices brevity for guidance.

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 the 0% schema coverage and no output schema in description, it only vaguely mentions return values. It does not address error handling or prerequisites beyond the checklist. With many sibling workflow tools, more detail on when to use this versus others would help.

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?

Schema coverage is 0%, so description must compensate. It lists both parameters with explanations: workflow_id as identifier and workflow_yaml as YAML definition. This adds meaning beyond the raw schema, though format constraints are not detailed.

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 'Modify an existing workflow using YAML definition', specifying the action and resource. It distinguishes from sibling tools like create_workflow and trigger_workflow.

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

Usage Guidelines4/5

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

The description provides a checklist for prerequisites and instructs to display diagram and confirm with user before execution, guiding when and how to use the tool. It does not explicitly mention alternatives but the context implies distinct tools for creation and triggering.

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