Skip to main content
Glama
ComplianceCow

ComplianceCow MCP Server

modify_workflow

Update existing compliance workflows using YAML specifications to modify states, activities, conditions, and transitions within governance processes.

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?

Adds the critical behavioral constraint to confirm with users before execution, but lacks disclosure on other behavioral traits like idempotency, transactional safety, or destructive side effects of updates.

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

Conciseness4/5

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

Well-structured with front-loaded purpose and preconditions; the mandatory checklist is lengthy but earns its place by preventing misuse, though the Args/Returns headers repeat standard schema info.

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 complete for a complex operation (workflow modification) given the output schema exists; the CCow schema checklist appropriately flags external knowledge dependencies.

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 effectively for 0% schema description coverage by explaining both parameters (UUID requirement for ID, structure expectations for YAML) in the prose and Args section.

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?

Clearly states the specific action (modify) and resource (existing workflow using YAML), implicitly distinguishing from sibling 'create_workflow' via the 'existing' qualifier and UUID requirement.

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?

Excellent explicit guidance with a mandatory 'BEFORE using' checklist, specific preconditions (schema knowledge), and required user confirmation steps that define when not to proceed.

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